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.
Git, probably
Please clarify, OP, did you mean
?
What about square screens?
inb4 chaotic neckpain
Indeed. Makes it more work to filter the handful of good or even great articles from the 99.99% that use this platform for its apparent ease of money grubbing.
It’ll probably take Valhalla for me, personally.
This seems to complicate it, and I imagine someone else would still need to do the footwork and/or it’d require C/C++ knowledge.
It seems like GDScript is already way less dynamic than Python and a bunch of optimizations has been done accordingly.
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.
I sure hope so, but I’m not overly optimistic tbh. The market is basically considered medical, therapeutic devices. It is as you imagine, probably worse. It isn’t easy to find prices directly, but the only way this range of vendors continues to exist in this niche market is to sell devices with the complexity of a keyboard for four to five digits. There is no competition worth talking about happening.
So unless very specific regulation takes place, I don’t see standardized access to braille displays happening.
Right, that is another item I wished more editors would have picked up. Besides - say - nested language modes.
Original poster is right by all accounts, of course. Now, let’s come up with exotic significant indentations.
function xyz(a, b):
| var x = 2
| if true:
| | do_something()
| else:
| | do_something_else()
| anyway()
Pro: Your editor no longer needs to implement indentation hints.
Con: Looks obstructive if not highlighted like an indentation hint.
Your turn.
That reminds me of those times when back on reddit some dev showed up to present their new GUI library. Bragging about how they were better than Qt devs etc. (even though they didn’t implement the hard parts, like working text fields or tables)
After some time a bunch of people had enough and started bullying those guys into submission about accessibility. After some time, every of those toolkits had support or at least plans for supporting screenreaders. Eventually, AccessKit became a thing.
Good times.
Of course, I might be overestimating how easy it is to get better braille oriented editors
A braille display traditionally is a personal, almost handfitted (estimated by price) device controlled by its screen reader software. Not the editor. This has some unfortunate implications:
So yes, you might be overestimating how easy that is, compared to telling some diva asswipe chucklefuck to use that formatter or work at McDolans.
I need it to steal content from programminglanguages.
I’m glad it doesnt.