deliriumchn

Well apple themselves are pushing swiftUI and I suspect it will be the main (and only) approach as time goes on, even though its just a wrapper around "older" approach...

no, not really, PQC is already being discussed in pretty much every relevant crypto thing for couple years alearady and there are multiple PQC algos ready to protect important data in banking etc as well

while jquery had a gajillion of exotic apis to do pretty much everything, react is, frankly, pure js with handful of apis: jsx (html with pure js), useState/useEffect/useMemo (rarely you need more), and initial hydration function. Rest is utility libraries, bundler, and all the wondeful things that brings you endless headache and depression because without them fulfilling yet another business req would take 10x more time

debugger is very far from being feature-complete, I would call it MVP at the moment; lets see if they will iterate on that or will quickly go back to new shiny thing...

they are not intrusive but their entire focus changed on that instead of other features. Entire Git view feels abandoned in half done state yet they spent entire month working on AI chats, AI agents, their own AI edit (that's priced 20 per month yet they boast how light and performant it is -- why isn't it free local model then and why its priced worse than copilot?)

They're moving from "making awesome code editor" into yet another "buy our ai" product

I hate the direction they're going to be honest with this giga focus on AI bullshit. Only good part added was zeta (their own predictive editing model that jumps across the file where it predicts you want to edit your typo etc AND have a "subtle" mode), but they price it at 20/month, which is absurd.

> I don't want to learn a complex framework. I don't want to learn magic that I don't understand without reading the documentation (useState, createSignal et al)

I'm always suprised reading statements like that. No offence, but maybe you're in wrong career if you don't want to learn how most popular and important tools of today work... Not to mention that its so simple you can learn everything required to be efficient during lunch break

According to Duo themselves its already included in duolingo max -- https://blog.duolingo.com/duolingo-max/

Yes, they use bing https://duckduckgo.com/duckduckgo-help-pages/results/sources...

Never understood this posts. React as a whole and state management became many times easier over the years (been working with it, vue and a bit of angular for 6+ years now).

Function components removed stuff like getDerivedStateFromProps and many other things, introduced clear and simple way of component updating (as in "prop reference changed, I'm gonna render now").

For state we got redux toolkit, which simplified reducers, zustand and recoil/jotai and mobx which allow you to pick based on your needs instead of writing million reducers or passing state to children when you don't really need it.

Its not "react got hard", its people unable to adapt to changing world. Every mainstream framework in reality got streamlined, simpler and more effecient to create apps.

I have a bad feeling that this will break modded beat saber on quest once again :/

> Nothing comes close to it in Go, Ruby, JS (Node), Python; from what I've seen. Laravel is one step ahead.

I can't really agree with that when Express and Django exists in this world. But Laravel is indeed amazing piece of software

quite enterteining that majority of "I don't like X" articles are coming from people who can't use the tool because they're lazy to understand basics

I could say that its interesting, but its instead region restricted (for android at least) and now available in Europe.

another month, another post complaining about react and claiming that its slow and hard... But its not hard, at all. Learning core react functinoality (which will let you make complex apps on its own) takes 2-3 hours (if you're a slow reader), and performance is fine. 99% of the time its not the tool, its the app's code being slow, and when its slow, its easy to fix most of the time

its on their main page, 1.95 euro per day, no calculator needed.

> But when you are still on a 2Mbps connection

What happens when you use modern apps on iphone 3 or first nexus phone? I don't understand, do people think that with better, faster computers and network speed we should focus on smaller and smaller apps and websites?

if bad results are returned, you still can reword your query to match it better. I would prefer to see related, or slightly related results instead of 0.

yeah, the text on their main landing page reads like a promo you see in a game; just a combination of fancy words lol

"Hono

Fast, Lightweight, Web-standards

Runs on any JavaScript runtime."

> It takes a few hours, maybe a day.

Even then, most of the times it doesn't take even an hour because majority of people will grab default config or use something that allows no-config (parcel, vite, etc)... Some are fine with default CRA for a long time until they really need something custom, for example.

> Why attach this to an IDE? I would think that simply letting an LLM control a terminal and make a commit would be the better approach.

This is a recipy for disaster imo, LLMs are not that good yet to give them the ability to act on their own

> Basically, Bun is a lot faster and simpler

Funny enough, I got our work project working with yarn berry (whatever number this was this summer) in 10-15 minutes, but I couldn't manage to do the same with bun. I'll try again now after they got few minor updates probably just to see if its better now...

These components look pretty good and very neutral design-wise, no screaming style, which is important for someone who's looking for a components library.

> nue looks a lot simpler to use

Than what? I couldn't imagine react being hard, maybe for novice developers that just start with programming in general.

> React and other frameworks spent so much effort abstracting the render loop

Considering how big is community adoption and teams that are working on big 3 frameworks, they're doing it not "just because" and not to make your app slower. There are reasons for this and this new library will learn them as well, just like svelte did with their reactive variables approach.

60hz and usb 2.0 in phone priced 800+ in 2023 is funny

For me its not about finding time, its about finding will to commit and actually do something. Usually I feel burned out and tired after work and just want to relax and do the bare minimum (watch a movie/play some games etc), not sit and learn another tech thing

> There is not much difference between a $100 pump machine and the expensive cafe machine

There is, actually, a lot of differences. Expensive machines have that cheap ones don't:

- multiple (2+) boilers so you can pour 2 caps/pour cap and steam/etc

- a lot less noise

- more consistent temperatures

- preheating

- as mentioned, more consistent steamers, but also precise control over them

- built-in grinder (most of the times mediocre one, but better than none at all, albeit most people who follow this hobby just buy a separate one)

- sometimes they can be controlled remotely

- other smaller things

Most importantly, they're usually a lot more reliable and well-built.

But yes, taste-wise difference will not be substantial, its more like paying for your own comfort if you really want to invest in coffee. Hand lever brewers can be just as good for a fraction of a price if you don't mind to take extra steps. Makes it more fun for some people actually.

> If you know the convention it's quite easy.

This is exactly the problem. Humans write code for humans, not for tailwind specialists and bots. It should be clear and easy to read unless there is a valid reason for weird code (optimisations, hacks that don't work otherwise etc). Tailwind introduces yet another convention where it is absolutely pointless to do so.

NGL tailwind is really nice to build new things and is absolutely amazing to create MVPs and small projects ...

but once you got to the point where you open a file and see 20+ classnames stacked in every div, which makes them unreadable, its just a mess. Love-hate relationships with this tool, but the idea is very good and this article mentions biggest selling points - its easy and very fast to use.

How superior it can be if it just shows a native canvas element and then draws custom stuff on it, which leads to funny bugs like 1 frame lag on iOS (OS detects touch and rightfully assigns a draw action, then flutter slaps its hands and reassigns with scroll action)?

> But I still don't understand why most companies still focus on React Native for their cross platform development.

Because it uses native components, which leads to native feeling apps. For bonus points, they added new engine that makes performance differences between react-native and native apps very small (unless you're working on interval trading terminal or games, which flutter does not handle as well). Plus its simply easier and entry barrier is non existent, therefore its cheaper.

> Google needs to do better marketing for the technology.

Dart as a language is a bad marketing for their technology. I also hate the amount of boilerplate I have to write and how weird it looks compared to RN/SwiftUI/Compose.