5 ms·

Wait, you're saying it's possible to write web code without typescript, react, and node?

hyperhello 3y ago
Interpreted languages are so improved by lengthy build processes involving compilers, linkers, transpiration, and sixteen different kinds of incompatible package formats, I don’t know why anyone would eschew them.
- lcnPylGDnU4H9OF 3y ago
  I often wonder if a given manifestation of Poe's Law[0] is intentional. It seems not in this case, but damn if this isn't real. [0] https://en.wikipedia.org/wiki/Poe's_law https://en.wikipedia.org/wiki/Poe's_law
- renlo 3y ago
  "transpiration"; is this the perspiration one gets when trying to use the JavaScript toolchain to transpile code?
ravenstine 3y ago
Node? Who uses Node for anything serious in 2023? Real backend coding today is done using Bun. And yeah, you can write something in JavaScript, but it definitely won't scale and will constantly throw errors. Pretty much all serious frontend code today is written in Typescript across the board. /s
anyfoo 3y ago
> typescript Well, the problem is rather, that JavaScript is a pretty bad language (nobody claimed otherwise, when it was designed in 10 days), so that using something like TypeScript makes it much better. Unfortunately your browser understands JavaScript, not TypeScript. That's the immense tragedy of web development: It's a giant pile of excrement, because it's built on several things that were never meant to be what they are used for today. It's also why I left a long time ago, and never looked back.
- twism 3y ago
  curious as to what you left it for that doesnt have this compile step
  - anyfoo 3y ago
    I didn’t leave it because of the compile steps, but because the extra layers, despite all their downsides, were far from able to hide the underlying impedance mismatch. I left over a decade ago and went back to low level kernel programming.
    - noizejoy 3y ago
      It’s good for everyone that different individuals have different likes and resulting priorities. Good that you found the one that makes you happier. And with any luck your preferred niche isn’t too overcrowded, so you don’t suffer from those negative side effects.
      - anyfoo 3y ago
        I did not intend to shit on web developers, by the way. It's not their fault, they just have to live with it. I just lament the history that lead to what they ultimately have on their plate. Early "web development" went tremendously wrong, owing partially due to the fact that the "hypertext" markup protocol and markup language were meant to be used in an entirely different way, and partially due to early hacks leading to early results in terms of "web applications". But those hacks came at the cost of making this layer sandwich in any way sane to begin with. In my opinion, everything else since is an attempt to find a way out of that mess. I was there when the web happened, though only watching from the side lines. I also remember that there were more fitting approaches early on, but a lot of them suffered under the Internet's explosive growth: Some of the "sane" stuff at least would have needed concerted efforts for plans that have to be executed over time. But the web was already a thing, and people desperately wanted to do certain things with it. The quick hacks for that were available immediately, and they were cool: "Hah, look what I can do. You can now get a travel itinerary through your city's public transport system from the World Wide Web. Isn't that amazing?" (At the time, it was.) I'm not saying you cannot have joy in web development. As you say, it just wasn't for me. For the reasons above.

Interpreted languages are so improved by lengthy build processes involving compilers, linkers, transpiration, and sixteen different kinds of incompatible package formats, I don’t know why anyone would eschew them.

lcnPylGDnU4H9OF 3y ago
I often wonder if a given manifestation of Poe's Law[0] is intentional. It seems not in this case, but damn if this isn't real. [0] https://en.wikipedia.org/wiki/Poe's_law https://en.wikipedia.org/wiki/Poe's_law
renlo 3y ago
"transpiration"; is this the perspiration one gets when trying to use the JavaScript toolchain to transpile code?

ravenstine 3y ago

Node? Who uses Node for anything serious in 2023? Real backend coding today is done using Bun. And yeah, you can write something in JavaScript, but it definitely won't scale and will constantly throw errors. Pretty much all serious frontend code today is written in Typescript across the board. /s

anyfoo 3y ago

> typescript Well, the problem is rather, that JavaScript is a pretty bad language (nobody claimed otherwise, when it was designed in 10 days), so that using something like TypeScript makes it much better. Unfortunately your browser understands JavaScript, not TypeScript. That's the immense tragedy of web development: It's a giant pile of excrement, because it's built on several things that were never meant to be what they are used for today. It's also why I left a long time ago, and never looked back.

twism 3y ago
curious as to what you left it for that doesnt have this compile step
- anyfoo 3y ago
  I didn’t leave it because of the compile steps, but because the extra layers, despite all their downsides, were far from able to hide the underlying impedance mismatch. I left over a decade ago and went back to low level kernel programming.
  - noizejoy 3y ago
    It’s good for everyone that different individuals have different likes and resulting priorities. Good that you found the one that makes you happier. And with any luck your preferred niche isn’t too overcrowded, so you don’t suffer from those negative side effects.
    - anyfoo 3y ago
      I did not intend to shit on web developers, by the way. It's not their fault, they just have to live with it. I just lament the history that lead to what they ultimately have on their plate. Early "web development" went tremendously wrong, owing partially due to the fact that the "hypertext" markup protocol and markup language were meant to be used in an entirely different way, and partially due to early hacks leading to early results in terms of "web applications". But those hacks came at the cost of making this layer sandwich in any way sane to begin with. In my opinion, everything else since is an attempt to find a way out of that mess. I was there when the web happened, though only watching from the side lines. I also remember that there were more fitting approaches early on, but a lot of them suffered under the Internet's explosive growth: Some of the "sane" stuff at least would have needed concerted efforts for plans that have to be executed over time. But the web was already a thing, and people desperately wanted to do certain things with it. The quick hacks for that were available immediately, and they were cool: "Hah, look what I can do. You can now get a travel itinerary through your city's public transport system from the World Wide Web. Isn't that amazing?" (At the time, it was.) I'm not saying you cannot have joy in web development. As you say, it just wasn't for me. For the reasons above.