p0nce

10 ms·

91.
by p0nce 3y ago
They are, H.265 have "slices" and "tiles" that allow parallel decoding.
92.
by p0nce 3y ago
Having maintained both C++ and D for different compilers, it's way easier to do it in D since the front-end features are the same (modulo builtins) and the stdlib is 99% the same.
93.
by p0nce 3y ago
VisualD if you're accustomed to Visual Studio classic it's pretty much the same.
94.
by p0nce 3y ago
If you read about diffusion of innovation, there is the classical example that cure for scurvy was known way before being adopted: t https://web.archive.org/web/20151022041843/http://www.idlewo...
95.
by p0nce 3y ago
I write D fulltime for my small company, published a framework that 4 other small companies use (or have used). D is really nice for the small ISV, but is also prepared to handle massive codebases (deprecated, packages, gradual typechecks,
96.
by p0nce 3y ago
Lack of interest maybe? I don't use grep, I use an UI that lets me click and jump to a file. Or the builtin search in my IDE.
97.
by p0nce 3y ago
I'll join the choir and say to not ever try to become an OpenGL expert. It's deep and kind of useless. First of all, if your application use OpenGL, either: - you've unlimited resources for testing and vetting drivers, and yo
98.
by p0nce 3y ago
I agree that the balance is way too often shifted in the way of overengineering, probably because of our field being skewed by "higher status" thinking.
99.
by p0nce 3y ago
While I agree mostly, you can overdo the "grug". For example it is possible to underengineer (underabstract?) a software for years until realizing that simple things are still complicated, and you forget to built good abstractions
100.
by p0nce 3y ago
OK, this was better than expected.
101.
by p0nce 3y ago
I tried Rust briefly and it had that "Ocaml" feel of solving a puzzle.
102.
by p0nce 3y ago
Users very rarely vocalize their need for speed and even less their need for simplicity. App size being low might as well be associated with "low-content" so not valuable, a lot of effort to seem less valuable in the end.
103.
by p0nce 3y ago
It's more that IM and AP are more beginner-level Goa trance and MFG/Bypass Unit/Oforia/Juno/many others are the real OG ;)
104.
by p0nce 3y ago
Modern remasters are usually unconvincing, but this one was. Also: UX (Ultimate Experience) one of the best in the genre.
105.
by p0nce 3y ago
Same but 36 and it never really got worse for more than six month (say, if you do exposure to loud sounds). Real minor concern for me.
106.
by p0nce 3y ago
My neighbour got it from the very first shroom use.
107.
by p0nce 3y ago
Apps shouldn't be able to "notify" you (by default), in the same way your home appliance are not interrupting you.
108.
by p0nce 3y ago
D accompanies you from prototype to production (with graduate enforceble constraints) so I find it very flexible and practical, and the highlights of my programming career tend to be in D. If you want native with a joyful creative process,
109.
by p0nce 3y ago
Same with VAT really. Yet some business just stay there.
110.
by p0nce 3y ago
Honestly maybe easier to just do it in aseprite, at first it will be daunting but in the end enjoyable.
111.
by p0nce 3y ago
Twitter doesn't show me the people I follow, and instead show people I "might like", in no particular time order. When I do interact, almost noone of my followers can see my post because I'm not an advertiser / paid
112.
by p0nce 3y ago
Now I imagine a list of similar personnalities for codebases: 1. The Sand Tower. 2. The Sacred Pile of Poo 3. The closed Clue Shop. 4. For the Family 5. The Spreadsheet 6. The Silent Trainwreck. 7. The Warden 8. Gilga-mesh
113.
by p0nce 3y ago
What's the downsides? Anyone have used Zig and could report on the good and bad?
114.
by p0nce 3y ago
Some other languages implemented in D: - Vox: https://github.com/MrSmith33/vox - Neat: https://neat-lang.github.io/ - Volt: http://www.volt-lang.org/
115.
by p0nce 3y ago
> Localizable or customizable keywords/operators. See lamdu IDE. > Deep support for an alternative to exceptions using a Failable<TResult, TError> type See Zig's solution.
116.
by p0nce 3y ago
Because I'm a sour individual :) did reuse demoscene teachings in homemade post-processing (CPU! thanks to all the in-talk about raytracers being fast on CPU, and well drivers).
117.
by p0nce 3y ago
Er, we once win a "scene award" with a demo. You are right there was plenty of talented programmers there (and the level has only gone up), but this is also an _art_ scene and to be able to work so long for free on something that
118.
by p0nce 3y ago
1. Ask people how much they will buy it (with their money), not if it's a good idea. 2. When they don't want to buy, ask why.
119.
by p0nce 3y ago
> To which I simply don't have an answer. D does it with gradual deprecation, and not too much at once, it is the best for deprecating stuff (you don't need to fix your code immediately) but there is always a residual complaini
120.
by p0nce 3y ago
So: D is bad because it needs more breakage! But at the same time D is bad because it needs less breakage. Right.

More ›