proposals
FizzBuzz Enterprise Edition
proposals | FizzBuzz Enterprise Edition | |
---|---|---|
15 | 329 | |
433 | 20,505 | |
0.2% | 0.5% | |
0.0 | 0.0 | |
over 2 years ago | 2 days ago | |
Java | ||
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proposals
-
An intro to TSConfig for JavaScript Developers
target - Specifies the ECMAScript target version for the emitted JavaScript. Defaults to ES3. To ensure maximum compatibility, set this to the lowest version that your code requires to run. ESNext setting allows you to target the latest supported proposed features.
-
Writing RFCs
TC39
-
Pipeline Operator great again!
Current Status: You'd have to check the TC39 proposals repository or the official proposal text for the most recent status. As of my last update, it had not yet reached Stage 4 (final stage) of the TC39 process, which means it wasn't part of the ECMAScript specification yet.
- Set methods proposal reaches stage 3
-
Upcoming ECMAScript features I'm excited about
More proposals can be found on the official GitHub page.
- What to learn in 2022
-
Updates from the 89th TC39 meeting
There were a couple of other proposals that made stage 1 too, can see here.
-
Don't make me think, or why I switched to Rails from JavaScript SPAs
The working group most in charge of JS is ECMA's TC-39 (TC => Technical Committee) [0]. They've been taking a very deliberate, slow path to expanding the "standard" library because they take a very serious view of backwards compatibility on the web. Some proposals were shifted because of conflicts with ancient versions of things like MooTools still out in the wild, for instance. (This was the so-called "Smooshgate" incident [1].)
This may speed up a bit if the Built-In Modules proposal [2] passes, which would add a deliberate `import` URL for standard modules which would give a cleaner expansion point for new standard libraries over adding more global variables or further expanding the base prototypes (Object.prototype, Array.prototype, etc) in ways that increasingly likely have backwards compatibility issues.
TC-39 works all of their proposals in the open on Github [3] and it can be a fascinating process to watch if you are interested in the language's future direction.
[0] https://tc39.es/
[1] https://developers.google.com/web/updates/2018/03/smooshgate
[2] https://github.com/tc39/proposal-built-in-modules
[3] https://github.com/tc39/proposals
- O que são RFCs e como elas funcionam na linguagem PHP
-
Ask HN: Where are the resources for complex architectures for Node.js?
My biggest pointer would be to remember that Java & JavaScript aren't named that way by coincidence. They're two different approaches to a similar problem. Java suffers from Enterprise Development (eg: Enterprise FizzBuzz[0]), JavaScript suffers from Ultimate Accessibility (eg: how many questions on Stack Overflow conflated jQuery and JS?).
> How should exceptions be managed? [...] Has there been a debate about best practice? Where can I find it?
I suggest you handle the errors you can and otherwise let it crash.[1][2] Debates in NodeJS-land have steered towards more monadic/Result-like structures and working synchronous-looking try/catch onto async/await. NodeJS and its various components are open source, you'll have a lot of luck looking around on GH for issues & PRs related to a feature -- same for the language, ECMAScript[3] officially.[4]
Since you mentioned Clojure, have you looked at ClojureScript?[5] That may be a good entry to JS authors & articles you'd enjoy.
> I have the impression that NodeJS is a bit more magical than the JVM [...] Is that correct? Where are good resources on this subject?
As other replies have mentioned, you're really talking about V8[6] for the "JSVM" executing that code. A thing I've seen throw some people for a loop is how minimalist the specification actually is.[7] The magic in NodeJS is certainly from V8 and the rate of optimizations there but also libuv,[8] what actually powers the infamous event loop.
Hope that helps!
[0]: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
[1]: Borrowing from Erlang, see Making reliable distributed systems in the presence of software errors, Joe Armstrong, page 104 "Error Handling Philosophy" https://erlang.org/download/armstrong_thesis_2003.pdf
[2]: _Most_ kinds of errors will cause the process to crash if you don't handle them, https://nodejs.org/dist/latest-v16.x/docs/api/errors.html . Promise rejections don't (yet) though it emits an error, and callback-based APIs will always consist of an [error, data] tuple for the arguments
[3]: https://github.com/tc39/proposals
[4]: Because Oracle owns the trademark, of course: http://tarr.uspto.gov/servlet/tarr?regser=serial&entry=
[5]: https://clojurescript.org/
[6]: https://v8.dev/docs
[7]: "ECMAScript as defined here is not intended to be computationally self-sufficient; indeed, there are no provisions in this specification for input of external data or output of computed results. Instead, it is expected that the computational environment of an ECMAScript program will provide not only the objects and other facilities described in this specification but also certain environment-specific objects, whose description and behaviour are beyond the scope of this specification except to indicate that they may provide certain properties that can be accessed and certain functions that can be called from an ECMAScript program." https://tc39.es/ecma262/#sec-overview
[8]: https://github.com/libuv/libuv
FizzBuzz Enterprise Edition
- FizzBuzzEnterpriseEdition
-
Simple Lasts Longer
That "Hello World Enterprise Edition" looks dangerously under-engineered - I could understand it! Far better to follow the best practices demonstrated in the Fizz Buzz Enterprise Edition...
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
-
Writing Clean Code with FastAPI Dependency Injection
Clean code is a balancing act - you’ll want to make sure you don’t turn your codebase into something like this.
- Milyen hasznos Github repokat ismertek?
-
Yazılım sektörünü bırakmaya değer mi?
Bu hocam https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition
-
oopWentTooFar
amidoingitright
- 7+ layer generic architecture libraries are crying rn
- Primeagen Code Review - EnterpriseQualityCoding/FizzBuzzEnterpriseEdition: FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.
-
Is Entreprise code unavoidable?
It seems to me that all large software projects eventually grow into "Enterprise" code. What I mean by this is something like FizzBuzz Enterprise Edition; large codebases with many layers where Design Patterns and SOLID principles are applied vigorously.
-
Java 21 makes me like Java again
???
I'll answer your question with a question: Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... ? :)
I'm guess that to those of us who remember when Java came out, "FizzBuzz: EE" is what we think of when we think of Java. :P
In Java I have to type a bazillion characters to get anything done! And make all these useless directories and files and InterfaceClassFactoryProtocolStreamingSerializer BS. And worry about how that executes.
C++? No bloat*, just speed
*Yes, there's some _optional_ bloat. But compared to Java? no contest.
What are some alternatives?
DIPs - D Improvement Proposals
Logback - The reliable, generic, fast and flexible logging framework for Java.
peps - Python Enhancement Proposals
awesome-functional-python - A curated list of awesome things related to functional programming in Python.
proposal-set-methods - Proposal for new Set methods in JS
Simple Java Mail - Simple API, Complex Emails (Jakarta Mail smtp wrapper)
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
yGuard - The open-source Java obfuscation tool working with Ant and Gradle by yWorks - the diagramming experts
temporal-polyfill - Polyfill for Temporal (under construction)
bitburner - Bitburner Game
proposal-change-array-by-copy - Provides additional methods on Array.prototype and TypedArray.prototype to enable changes on the array by returning a new copy of it with the change.
Java-Hello-World-Enterprise-Edition