Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
90s_dev
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
39 ms
·
601.
▲
by
90s_dev
1y ago
Yeah he talks about how it was a choice he made simply so he could get stuff done and have some end in sight.
602.
▲
by
90s_dev
1y ago
It's not that they're hard to understand, it's that they're much denser . From Factor's examples page: > 2 3 + 4 * . There's a lot more there to mentally parse than: > (2 + 3) * 4 It's the same as w
603.
▲
by
90s_dev
1y ago
Popularity comes from utility. Utility comes from the right trade offs. Limitations demand careful trade offs.
604.
▲
by
90s_dev
1y ago
- 320 x 180 screen size for starters - Limited map size - Limited color palette I think - and more!
605.
▲
by
90s_dev
1y ago
const o = {} o["foo"] = function(){} o["foo"]() let key = "foo" o[key]() key = Symbol.dispose ?? Symbol.for('dispose') o[key]() o[Symbol.dispose]()
606.
▲
by
90s_dev
1y ago
Limitations demand and produce extraordinary creativity. That's the secret behind pico8 and Animal Well and so many amazing games. I wish I didn't think of a significantly better architecture for my 2d-pixel-art-game-maker-maker t
607.
▲
Animal Well taps into PS5 hardware to elevate 2D pixel-art platforming
(blog.playstation.com)
3 points
by
90s_dev
1y ago
|
0 comments
608.
▲
by
90s_dev
1y ago
JSX is my favorite thing to come out of Facebook (also the only good thing).
609.
▲
by
90s_dev
1y ago
Using is more flexible, since it doesn't need a function call, but can simply assign a variable that implements [[dispose]]
610.
▲
by
90s_dev
1y ago
When I discovered this feature, I looked everywhere in my codebases for a place to use it. Turns out most JS APIs, whether Web or Node.js, just don't need it, since they auto-close your resources for you. The few times I did call .clos
611.
▲
by
90s_dev
1y ago
Lisp I can understand to some degree... but writing Forth for a living? I know about 20-30 languages, but that one is Greek to me.
612.
▲
by
90s_dev
1y ago
For starters, your code is so full of serious syntax errors that in some places it's not even close to valid JavaScript. This is my best guess reconstruction: (async (e) => { await doSomething() while (!done) {
613.
▲
by
90s_dev
1y ago
There's just something more polished, aesthetic and functional about the choice of limitations pico8 offers, whereas tic80 encourages decision paralysis.
614.
▲
by
90s_dev
1y ago
I've never had an issue with =nil being delete. What problem does it cause?
615.
▲
by
90s_dev
1y ago
Well of course you can trick people who aren't familiar with its syntax. But people who are see that this is local print = print("hello"):format() local foo = func("args to func"):itreturnedatable("!
616.
▲
by
90s_dev
1y ago
This sounds like it could compete with V8 at some point in the next few years. Honestly it could be a game changer. Looking forward to watching its progress.
617.
▲
by
90s_dev
1y ago
Ha! Called it again! But why gotos instead of proper control flow? Is it just easier to emit?
618.
▲
by
90s_dev
1y ago
That's really exciting work. Great job. Hope it's fulfilling.
619.
▲
by
90s_dev
1y ago
No it was me who misunderstood you. And I kind of agree. I've never been a fan of tagged template literals. It gives you no autocompletion, no type checking, no syntax highlighting, nothing. And it requires a runtime string parser. I g
620.
▲
by
90s_dev
1y ago
That's actually really exciting in that case. If it goes further and generates native C control flow statements when possible ("if", "for", native functions, native function calls, etc), I think it could be an omni-
621.
▲
by
90s_dev
1y ago
`...` and fn`...` in JavaScript are just syntactic sugar for function calls, the former for array.join(...) and the latter for fn(...) so there's no issue with these utilizing the current scope since that's what all function call
622.
▲
by
90s_dev
1y ago
Oh wait I know why. It's because the PIP had no specialized syntax highlighting to show that it was getting the variables from scope. So I started reasoning about it differently than I do about JS string literals, rather lazily too, an
623.
▲
by
90s_dev
1y ago
This visualization is breathtaking, thanks for making it. Sometimes I want an excuse to write some Rust. I think I'll make one in my upcoming web app, since it already uses web workers. I guess the side effect is that wasm (and therefo
624.
▲
by
90s_dev
1y ago
Can I quote you when I finally release my app in a week or two?
625.
▲
by
90s_dev
1y ago
Wait, Pallene just compiles to C using whatever local C compiler? https://github.com/pallene-lang/pallene/blob/master/src/pall... Well that's kinda disappointing. I expected something more in 2
626.
▲
by
90s_dev
1y ago
> Or they'll write to me and say, "how do I know if it's evil or not? I don't think it's evil, but someone else might think it's evil, so I'm not gonna use it." > Great. It's working. My li
627.
▲
by
90s_dev
1y ago
> But lua isn't like that. It's not weakly typed like javascript - it's more akin to pythons dynamic duck typing system What? No, Lua's type system is practically identical to JavaScript's. Even metatables are
628.
▲
by
90s_dev
1y ago
Now I'm on the fence about adding philosophy to software licenses, even if only in a joking way. It can be fun and even thought provoking, but it could get in the way of genuine business adoption for basically no return (you never know
629.
▲
by
90s_dev
1y ago
About 15 years ago I made a custom MIT or BSD license that added: "You agree to think carefully and always reflect about what you do and why you do it" or something to that effect. I thought I was so clever at the time.
630.
▲
by
90s_dev
1y ago
The only keyboard thing similar to that I ever used was the full keyboard cover that came with the Flintstones PC game.
More ›