sbjs

I'm glad we're in the age of static typing. The age of dynamic typing as a response to incorrect static typing was a necessary evil. We had to take a break from broken languages in order to realize what needed to be fixed in those languages. I'm convinced that JavaScript will eventually be one of the best, fastest, and safest languages, as long as we keep this cycle up of abandoning necessary languages and returning to them with very thorough fixes to much better understood and detailed problems with them.

Can anyone get this working? I followed all the instructions in the readme and can't get it compiling.

That was literally the point of Java, to be syntactically and semantically simple, in contrast to the extreme complexity of C++. But just like with Lisp, that only moves necessary complexity to another layer. True wisdom in language design is understanding the line between necessary and unnecessary complexity, and perfectly incorporating necessary complexity into the language so users don't have to reinvent the wheel at the library or precompiler level.

I guess that’s where I draw the line too. And I generally don’t even write software anymore because of that. Everything’s pretty much been done. The few websites I do need to maintain, though, I’m gonna make sure it’s something that isn’t a painful experience the whole time. Hence my custom SSG.

I have a few difficulties working on ordinary web CRUD apps:

1. I'm really bad at memorizing things, I'm better at memorizing principles. Which makes most APIs like Rails and Django difficult for me. This is probably why I ended up writing my own SSG where everything is just a Node.js import, even HTML is (via JSX, via my own lightweight runtime).

2. I'm really bad at accepting doing things the wrong way when the right way is so much better and obviously so. For example, I struggle to force myself to use EJS or any traditional express-compatible templating engine. This is also why I wrote my own on-top-of-node runtime with JSX support.

Two problems with that theory.

1. I'm using some external stuff, just not others, so where do you draw the line?

2. I've been doing this for my whole 15 year professional career. Doesn't seem like a phase.

It's not even that. Like, that article itself was generated by a SSG that I wrote myself because I wanted to use JSX on the backend without being anything like React (it's rendered as plain HTML by this runtime function[1]). Web or not, I just can't help but do everything differently than everyone else does.

[1]: https://github.com/sdegutis/sdegutis.github.io/blob/main/app...

That was a really fun challenge and helped me freshen up on some skills I forgot I had. Thanks for that.

SEEKING WORK | REMOTE or Chicago

Web, desktop, and mobile

15+ years professional experience

Severely discounted rate of $30/hour

Open to small, short-term projects

Keywords: TypeScript, JavaScript, React, Vue, JSX, jQuery, Express.js, Node.js, DOM, Electron, Stripe, AWS, C, Lua, Ruby, Python, Objective-C, Swift, C#, Java, Clojure, Bash, Rust

This is the most unreadable code I may have ever seen. Congrats on successfully writing it and getting it to work.

I remember having my kids install MuseScore and it was an invaluable app for getting your feet wet with music making.

This is such a shame. One of the most powerful features of the SDK is now exclusive to the site itself. I can see the incentive to make this decision, but it's also going to have counterproductive results for the same reason.

And rightfully so. Why maintain a feature for a small minority? Let them fork and maintain it themselves.

Closer analogy would be .pyc files. Precompiled bytecode.

Because I want to store my document's data in a standard text-only human-readable human-editable format, but be able to do the majority of my writing more easily and with wysiwyg which is an free, automatic and space-conservative preview.

Everything worthwhile about Lisp has been integrated into TypeScript and JavaScript.

There’s certainty a nostalgic emotional reaction when seeing these but it’s not strong enough to move me to prioritize trying out esoteric technology over the other million interesting or necessary things on my plate.

I hope they codename it Dine.

I tried it before and it's not as easy as it sounds. There is no one spec, it's a handful of RFCs and other ad hoc extensions that are barely documented anywhere. I think there's at least a dozen different documents you have to refer to.

My personal guess is that most people need "warm up" time to make progress on their projects, the time needed to build up the mental model of the whole domain. This can go from hours to days to weeks depending on the person and the type of mental model. But some people have certain domains where they can just instantly build up that model in their head and immediately begin making serious progress. You sound like you're one of the rare ones that can do this for a large number of domains (3d algorithms, project architecture, database structure, feature interaction). I'm only like that with a few very specific domains and I suspect most other devs are like me in that sense, so we stand in awe when someone has that natural in-built capability. (I think this not only goes for making progress but also learning new concepts, as I have seen other graduate students who can blaze through certain things like Haskell where I struggle as through molasses.) If this theory is true, then you probably aren't spending more than 3-5 hours on projects like this per week, but you're making the same progress most of us would need 2-5 weeks for. Btw I'm the guy who posted your project and emailed you, thanks for coming here to answer our questions and thanks for making such a cool project and making it freely available for all of us to learn from!

It backfired ;)

I didn't notice anything off about it. Looks normal to me.

Does this mean you effectively get it "free" in terms of CPU cycles, and can use the CPU for all 16ms (60fps) of each frame to do game logic, without worrying about render time?

I actually found it here

https://github.com/uhub/awesome-c

I don't understand how 3d games are written or know what shaders are, so this is complete magic to me, and I'm surprised it's only 5k lines of C code!

I love traditional simplistic UIs like Win95 for their retro feel, and miss the days when you could skin apps. That ship probably sailed by now, but at least we get projects like this every once in a while.

But isn't Windows 95 not allowed to be used unless you purchase a license?

As unfortunate as that may be, I'm glad to hear that maybe it's not that I can't learn Haskell, maybe it's just that I chose the wrong book. So here's to trying again with Hutton's book!

[Comment redacted for being not well thought out and more cynical and less positive than I'd like to be]

I would love to see a wasm repl online. Something that's focused on teaching the language, not for people who are going to write compilers that target it, but for people who are confused about what it is and how it works, as a way of demystifying wasm so that they have more confidence in choosing to adopt it. Maybe something that really visualizes the ins and outs of a wasm program, and maybe some kind of dynamic visualization of how the s-expressions transform into stack-based code. Just an idea, but I think it could be useful and fun for someone to make for those of us who want to play around with wasm without installing anything :)

And how does this work if it involves an open file handle, or some other non serializable state?