I find it weird that they use so many euphemisms for death when its the main motivation for the feature here. Is it really that uncomfortable for some?
In what context would one realistically be able to debug TCP/IPv4/IPv6? Also in terms of network sockets and kernel implementation you're talking about apples and oranges.
>I am a collector of swag from large companies that have collapsed due to anything from mismanagement to outright fraud
This is why I log on to this site.
The Wireless+ system from AIAIAI is a significant improvement in this space. I've never had the need for a low-latency lossless audio signal but even nowadays bluetooth seems kind of clunky.
Regarding shortcuts: one that often gets overlooked is Move focus to next window under Shortcuts > Keyboard which lets you cycle between windows of the active application. I have it mapped to ⌘`.
Depends a lot on what type of programming you're interested in doing and if you're willing to pay for lessons. I think scrimba.com is a great resource for front-end related stuff – and not to mention a great platform for making programming lessons.
I get the argument, though I wouldn’t call it unique given how long JS fatigue has been a thing. HTMX is just one piece of the puzzle though so a more correct comparison would be a mature application built with htmx vs say sveltekit, not a list of cherry picked htmx features.
Agreed. Judging from this example: https://github.com/rajasegar/htmx-trello which uses htmx in pug templates combined with hyperscript the results are... dubious and hardly scalable.
In that case it would be much more interesting to read about the "hypermedia approach" including its own downsides. For instance, the differences between SPA/MPA implementations are also directly linked to developer experience – most people simply prefer business logic to live inside components. Is that possible using a hypermedia approach? Who knows, but "we think our library is great" isn't particularly an instructive or interesting way of discussing this topic.
No, the entire point of borrowing the term transitional is "having the best of both worlds". The SPA/MPA comparison is about highlighting the best aspects of each method and envision ways of implementing both. Any decent framework nowadays can be used to implement "transitional" features, so HTMX using this as a way to plug their own is lazy and annoyingly counterproductive in this particular discussion.
I'm sorry but what's the point here? Rich's talk was not even remotely aimed at HTMX yet this article is nothing but a shameless list of HTMX features.
I believe the JS criticism is more about the culture and ecosystem than the language itself. In short: Most if not all JS devs are more interested in playing with specific tools and APIs rather than dealing with and/or implementing programming patterns and principles. In the last decade "small modules" skyrocketed the popularity of NPM and a lot of people pushed the idea of "don't reinvent the wheel just 'npm install' everything" and sadly it stuck. Basically all JS-related discourse reduces down to "use X instead of Y!". It started with packages, then libraries, then frameworks, and now meta-frameworks – hell even meta-meta-frameworks if you count the people raving about Blitz. It's like that period when young devs couldn't tell the difference between jQuery and JS but way worse. So yes, in a way you are in fact cheating your way out of software engineering by installing neverthrow or whatever. I mean the language is already pretty damn high-level already.
Is the "exciting" part that these new meta-frameworks save you from actually having to learn and implement proper front-end development concepts? Remix is an "inflection point" because now you don't have to learn how a server-side rendered website works. Tailwind is an "inflection point" because now you don't have to learn how a design system works, let alone how to implement one. Copilot is an "inflection point" because you no longer have to alt-tab between your code and google, or remember how regex works. It goes on and on.
Love this trick. It should be noted that the element is added to the window object as long as the id follows the syntax of a valid javascript variable (meaning no dashes).
As long as your code doesn't need transpiling, there's also the possibility of importing modules using the type attribute in script tags: <script type="module" src="script.js"> – which is very well supported: https://caniuse.com/es6-module
If I had the time I would try out the notebook API to make a simple node.js notebook. There's one alternative that works great but is too bloated to my liking:
Which again is weird for someone like Ive considering that "form follows function" is one of those mantras that people like Rams and the Bauhaus folk based their entire work on.
Switching to fullscreen keeps everything below the notch, judging from the screenshots. I'm betting they'll add an accessibility option to keep the UI below the notch as well.