8lall0
8lall0 on Hacker News
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.
That's literally the worst.
Literally, my two thoughts:
- Am i still learning something here?
- Am i earning enough here?
If the answer is NO to both of the questions, then i know that it's time to leave.
My only question is: why?
1) No, no, no, please avoid stuff that needs to be indented in 2021. YAML is more than enough to prove that is a silly thing to do.
2) If your configuration file is too big, maybe you're doing it wrong.
3) TOML is by far the less ugly format for configurations that i've ever used. Far from perfect, but it's predictable and doesn't require indentation.
I mean, if you don't consider the fancy structure, it's pretty doable for cheap. GG
I did HTML email coding for 4 years and it's absolutely the WORST.
I see only one reason to use custom JS UI stuff in a project: if it's an internal tool and you and your colleagues (and all your tech department) use those components when programming.
Otherwise i would use a framework, it's much reliable. If you don't want to deal with the React/Angular complexity, try Svelte, it has the best dev experience if you come from vanilla JS development.
I don't, but on bad screens it helps with eye fatigue (at least, in my experience).
Now that i have a decent IPS, i don't need it anymore.
I - honest to God - think that this isn't a good idea: it makes the HTML basically unreadable, plus if you end mixing up Turbo and plain CSS sheets it's gonna be a manteinability mess since you have to costantly look on (at least!) two different places.
You can export your SVGs with fill="currentColor" and your color attribute onto the SVG tag or its container would work.
Since at $JOB i'm using SVG icons with more than one color, i use fill="var(--svg-color-base)" or fill="var(--svg-color-accent)" so i can precisely set which color i want, in a perfectly scope-able manner.
The greatest advantage is that you can reference externally your svg with xlink.href on top of your website: you have to make one more request, but it's cacheable. Pick your tradeoff :)
That's because he's using React, i'm using an svg sprite sheet in a simple html page, with native <svg> tag and works like a charm.
If your svg set is small, you can even inline it: you lose cache, but you save a request so you can choose your tradeoff.
Give hugo a chance.
You can even setup hugo + github pages with a simple script. You fire the script, it compiles and push everything in the right places.
If you don't feel confident about theming, pick one from the website and you're good to go.
