Just try, what is the worst that could happen? Hehe-- [sound of breaking bones and rupturing organs]
Just try, what is the worst that could happen? Hehe-- [sound of breaking bones and rupturing organs]
Oni would be great, problem is the rights to it are split between like five different studios and it’s effectively abandoned. It’s why it’s not on GOG, Steam, etc.
Possibly the same situation for Attack of the Saucerman. Dayum.
It also wouldn’t surprise me if the source code has been completely lost, meaning there’s no chance of an HD upscale or anything.
Oh well, realistically, an upscale and a few improvements wouldn’t have cut it anyway.
On second though, it doesn’t seem like a big improvement. Reminds me a bit of limbfeeders without limbs.
This, it would be less deep in the uncanny valley without eyes at all.
What about square screens?
inb4 chaotic neckpain
Unfortunately nobody in charge has seen consequences for their decision to save a few theoretical nickels, so far. But then again, a lot of software/IT related stuff would look completely different, if anybody did.
Or a signal that you’d rather not support the worst way to introduce type systems to frontend dev. While I’m not sure that applies to DHH, I am sure there are other devs that understand compromising all your goals to codepend on Node or even JS itself isn’t that much of a win and rather see support for better options.
but I could see it being a good step forward for more meaningful features to be added in the future.
I think you are right. And that is unfortunate.
My bad, I’m not deep enough into our frontend stack to realize Hjeilsberg already did what he does best - ruining enums. (I guess he is not to blame for global imports in c#, so i can not add ‘questionable import module/namespace ideas’.)
And it seems like this proposal contains type declarations (in order to compensate for their enums), among other typescript specific things. So, guess it is option B, then.
That’s not a positive, though.
Depending on how it pans out, it’s either not useful enough. Who the hell doesn’t use namespaces or enums. Or - as
These constructs are not in the scope of this proposal, but could be added by separate TC39 proposals.
implies - a door opener to outsource TypeScripts problem unto other peoples and not to investing into improving WebAssembly. That’s just MS being lazy and making their problems other peoples problems.
I feel like this would be the ideal scenario: things working right out of the box without needing a compile step or additional tooling.
It’s just annotations. No proposed semantics of a type system which your browser could check on its own.
That for sure looks fancy. Well, if I could draw to save my life, I’d definitely include it.
Requested: A clown version of the Critters-posting-on-4chan meme, with a horn on the desk and a red nose put around the screen.
Thanks!
Good bot. In fact, this might be the only bot that’s actually useful. Until we get spelling a bot for a-and-e mistakes.
The way it works is if you place 2$ you get the chocolate flavored condoms, but if you instead put 2$ then you get the Asian condoms.
✅
[answer accepted]
Makes sense. At first I thought you have to turn your coin around.
That guys’ as well.