Post AkyM4mOgrWyeUCixYu by steely_glint@chaos.social
(DIR) More posts by steely_glint@chaos.social
(DIR) Post #AkyM4k7bK67RQciHeC by mcc@mastodon.social
2024-08-14T21:01:04Z
0 likes, 0 repeats
What I want out of a programming language is to be able to take a four-year-old domain-relevant hello world project, clone it, build it, and have it still work like it did four years ago. Python cannot provide this. JavaScript/TypeScript/npm cannot provide this. I have not been using Rust long enough to know if Rust/cargo can provide this.
(DIR) Post #AkyM4lJKtx6H7JDAZs by nazokiyoubinbou@urusai.social
2024-08-14T21:31:26Z
0 likes, 0 repeats
@mcc At this point I am convinced that the only single thing in the world that can do it is either a VM that you made four years ago and haven't updated once sinceor COBOL.
(DIR) Post #AkyM4mNyuAPUS0OOSO by mcc@mastodon.social
2024-08-14T21:01:17Z
0 likes, 0 repeats
(C++, of course, is not possible to compile under any circumstances.)
(DIR) Post #AkyM4mOgrWyeUCixYu by steely_glint@chaos.social
2024-08-14T21:41:05Z
0 likes, 0 repeats
@nazokiyoubinbou @mcc Or Java - which is effectively both your options rolled into one.Semi seriously - I have production code that includes : if (_javaVersion.startsWith("1.4")) - jdk 1.4 was supported in 2002-2008The code still works.
(DIR) Post #AkyM4muawuUw59eRI8 by mcc@mastodon.social
2024-08-14T21:41:28Z
0 likes, 0 repeats
@steely_glint @nazokiyoubinbou Actually, I can believe java could pull this off.…but not C#.
(DIR) Post #AkyM4nWWfsq5ynOjPk by interfluidity@zirk.us
2024-08-14T23:09:25Z
0 likes, 0 repeats
@mcc @steely_glint @nazokiyoubinbou there’s lots not to love in JVM world. but i still use libraries I wrote 25 years ago. their ancient ant builds would still have worked, though I’ve migrated them to better tools for my own sanity. four years is like a blink in JVM world. those are new, “modern” projects.
(DIR) Post #AkyM4noxZLaIty1S9A by mcc@mastodon.social
2024-08-14T21:04:05Z
0 likes, 0 repeats
Incidentally, the solution to my baffling webpack error above was to run it like "NODE_OPTIONS=--openssl-legacy-provider npx webpack". That is fricking terrifying.
(DIR) Post #AkyM4ptHsEEbJy3wAa by mcc@mastodon.social
2024-08-14T21:25:10Z
0 likes, 0 repeats
Update: Okay so actually `npx npm-check-updates -u` fixed my package.json to fix this problem entirely and just worked on the first try with no additional new upgrade-related problems. But I'll still note the process would have been a lot faster and more convenient if the circumstances had not required me to wallow in despair for 20 minutes first
(DIR) Post #AkyM4sIWvLcAmpt7nE by mcc@mastodon.social
2024-08-14T22:56:01Z
0 likes, 0 repeats
Anyway uh I thought late this afternoon I'd sit down & make a lil self-contained typescript project but my old typescript hello-world "fork me" project didn't, uh, work with modern Node. So I fixed it. If you want a "TypeScript, WebPack, Preact already set up" project, here you go:https://github.com/mcclure/ts-helloBranches currently working:- stable (basic preact install)- state (recommend; comes with some helper classes for making useState more user friendly)- no-preact-or-react (self explanatory)
(DIR) Post #AkyM4v8iMIXtbGJpPU by mcc@mastodon.social
2024-08-14T22:57:23Z
0 likes, 0 repeats
Note: For many purposes you will probably want to start by editing tsconfig.json to change the ECMAScript compatibility level to something more recent than ES5. The fact that's my compatibility target should probably give you a sense of how long I've been using this hello-world project.(Also, that compatibility target is the reason the react [rather than preact] branch is still broken RN.)