8lall0

Imho, while i agree on the marketing side of the problem, there is one more, and probably, worst problem: at $JOB, every single PHP you're going to find has to be treated as legacy, no shiny stuff, no proper sane way to work with it, incosistent envs unless you're lucky enough to have a dockerfile and some scripting that can do the heavy lift for you.

All of this for the second lowest wage after JS devs. Not worth it.

I'm using Go and i'll never go back in the immediate future: go run . and i have all of it. Period.

PHP should strive for something like this.

Pretty odd article.

WASM is not so supported, but it's not like a major technology right now.

If you need complex UIs, separate backend and frontend and write the latter in something well supported (like, i dunno... JS)

"The days of crappy NPM packages are over" said no one ever, and no one will ever say.

TS is never going to catch up with Go performances, and the lack of IPC and true concurrency actually is very bad for backend services that need to handle stuff.

I think the OP wants to use Go for stuff that isn't supposed to do with.

Javascript: please stop using it. Period. XML: please stop using it. Period Period Period.

Liteally "oh i love Teslas, why my Nissan cannot behave like that?"

As a coffeegeek myself, i would like to see a video before!

While i can agree, Js is such an inefficient beast that using more efficient languages is IMHO mandatory.

No JS written tool will ever be faster than, for example, esbuild (Go).

Solar will never take over PER SE. It's intermittent and storage is expensive and inefficient.

I hate those articles where you put the one-solution, the energy problem must be addressed with multiple solutions.

Do you have 5 minutes to talk about TOML?

I am amazed by the amount of limits the community is pushing with a pico. If only the rp2040 had an integrated DAC...

Addendum: no spam no adv, i suggest the web dev, css and js online courses from Jonas Schmedtmann, i learned from his courses and he's absolutely a nice teacher.

3 months for web-dev is a very short period of time.

Web Dev takes a lot of exercise and expertise, plus CSS and JS are beasts that are completely different from more "classical" languages (like PHP).

Take your time, start from the basics (HTML, CSS and modern JS) and THEN try to use React. The world is full of React devs that don't know JS, you can be different and more proficient.

I would say RN, more community support if you're using it for business.

Hell no, horrible language, too verbose.