Java-Hello-World-Enterprise-Edition
htm
Java-Hello-World-Enterprise-Edition | htm | |
---|---|---|
24 | 42 | |
80 | 8,556 | |
- | - | |
0.0 | 0.0 | |
over 4 years ago | 3 months ago | |
Java | JavaScript | |
- | Apache License 2.0 |
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.
Java-Hello-World-Enterprise-Edition
-
Building a Streaming Platform in Go for Postgres
If you judge productivity by lines of code, absolutely.
https://github.com/Hello-World-EE/Java-Hello-World-Enterpris... is an excellent demonstration of this.
-
You probably should avoid putting lifetime parameters on traits
This reminds me of the "enterprise programming" mindset in OOP where people would make factories, strategies, strategy factories etc. just for the sake of it (instead of those solutions serving a real need) and ending up codebases that look like Hello World enterprise edition.
-
Simple Modern JavaScript Using JavaScript Modules and Import Maps
No other language or framework seems to get the same scrutiny as JavaScript.
The Enterprise Java solutions never seem to get as much discussion but we all recognize it also as being equally if not more so absurd[1]. This is true of every language and framework that gains mass adoption and use. Scala projects are crazy complex, the python 2 to python 3 migration was a mess, none of these are problems. They reflect the improvements in every metric to the underlying platforms and systems - end user experience, developer experience, reliability, testability etc.
JavaScript is in a phenomenal place today - we have come "full circle" but with better tooling, new capabilities, improved experiences etc.
There's a lot of keeping up with the jones' - that's partly nice as its job security and partly nice as a reflection of engineers improving our own ecosystem.
[1] https://github.com/Hello-World-EE/Java-Hello-World-Enterpris...
-
My first programming assignment was to print hello world, and my teacher said to always be very descriptive with my variable names. How'd I do? :D
It’s bad, but not as bad as the enterprise edition
-
Write the most complicated code for a "hello world" message
Hello World Enterprise Edition - https://github.com/Hello-World-EE/Java-Hello-World-Enterprise-Edition
-
Ever wondered why banking sites suck?
You might actually have to think about writing longass assembly hello world, but I can spin up fifteen Enterprise Java Hello World APIs in an afternoon.
- Java's Cultural Problem
-
Your death countdown begins... Your fav programming language decides your fate (read desc.)
Haven't written Java in years, but I'd take an enterprise edition program written in it, much like this one: https://github.com/Hello-World-EE/Java-Hello-World-Enterprise-Edition
- Well, that's one way of removing diacritic marks
- Personally I only listen to my boss complaining I make memes at work
htm
-
VanJS: A 0.9KB JavaScript UI framework
The preact team also dislikes transpiling jsx so they've developed an alternative using tagged template literals: https://github.com/developit/htm
-
React SSR web-server from scratch
So getting this to work without bundler magic is very hard. It's not surprising why NextJS is investing in a bundler. Though one thing that really sticks out is how much complexity we add for just miniscule dev ergonomics. Not using JSX and using something like htm would make all this easier (removing the bundler entirely), it's a lot of overhead to avoid a couple of quotes. React should really have a tagged-template mode. Also all of this is indirection is actually bad for dev ergonomics too! One of the reasons I did this is because I'm absolutely sick of magic caches and sorting through code that's been crushed by a bundler into something I don't recognize and can't easily debug. While we can't get rid of this completely (ts/jsx) this preserves the module import graph completely on the client-side making it easy to find things as you are working and preserving line numbers. This obviously is not useful for a production build and there's a lot of work that would need to go in to support both modes over the same code, but it's depressing no tools really work like this for local development.
-
HTML Web Components
You can also do JSX and skip the build step with preact + htm : https://github.com/developit/htm#example
-
Service Worker Templating Language (SWTL)
While I was able to achieve this fairly easily, the developer experience of manually stitching strings together wasnt great. Being myself a fan of buildless libraries, such as htm and lit-html, I figured I'd try to take a stab at implementing a DSL for component-like templating in Service Workers myself, called Service Worker Templating Language (SWTL), here's what it looks like:
-
Gaseous - Yet Another Games Manager
I would however highly recommend https://github.com/developit/htm
-
Create and Hydrate HTML with HTM
I thought the same thing, but apparently "HTM" is a JSX like javascript string template representation of HTML, and it can be found here: https://github.com/developit/htm
-
Anyone using React from just a CDN, barbarian style?
If you're going to do a no-build approach, assume modern JS (so you don't have to transpile the JS syntax). Also, you can use https://github.com/developit/htm as a nearly-identical equivalent to JSX syntax, also without transpiling.
-
Simple Modern JavaScript Using JavaScript Modules and Import Maps
This seems like a case of caring way too much about something that's hardly very different. JSX versus tagged template strings can be incredibly similar to one another.
The examples in this article are using vanilla template strings to author raw html, but that only misses a couple of nicities JSX has. There are tagged template string libraries like htm[1] that do include some of the few nicities JSX has, but which are actually compatible with the official language.
[1] https://github.com/developit/htm
-
A few programming language features I’d like to see
The first one exists in JavaScript and is called Tagged Template Literals. I agree with the author that its a nice feature. It's the perfect construct to use for prepared SQL statements, LINQ-style queries, or reimplementing a JSX-like syntax (see HTM https://github.com/developit/htm).
-
Using React without JSX == no build
There is however a library that is closer to JSX (HTML-like feel) but yet does not require a build step. htm. HTM uses tagged templates to leverage template literal as native Javascript template strings. If you have not played with tagged templates, I encourage you to check this out, it's a quite powerful feature, that has recently become a part of Javascript.
What are some alternatives?
FizzBuzz Enterprise Edition - FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.
jsx - The JSX specification is a XML-like syntax extension to ECMAScript.
subworld - Esoteric programming language where all instructions and data are either "hello" or "world"
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
rust - Empowering everyone to build reliable and efficient software.
esbuild-plugin-alias - esbuild plugin for path aliases
samples - JavaFX samples to run with different options and build tools
babel-plugin-react-html-attrs - Babel plugin which transforms HTML and SVG attributes on JSX host elements into React-compatible attributes
javalin - A simple and modern Java and Kotlin web framework [Moved to: https://github.com/javalin/javalin]
vim-jsx-pretty - :flashlight: [Vim script] JSX and TSX syntax pretty highlighting for vim.
NullAway - A tool to help eliminate NullPointerExceptions (NPEs) in your Java code with low build-time overhead
lit - Lit is a simple library for building fast, lightweight web components.