Unfortunately, the problem with Nim (as well as D) is the lack of big player support jump starting public opinion. Languages are inherently vendor-locked* (There isn't any way to foolproofly translate code from language…
>I prefer a nicely sandboxed and secured EME plugin over the insecure and clunkly silverlight pipelight trickery that was necessary before. What's the difference between the two? Why do you think the EME plugin is any…
What about prgmr?
>data on which they (should) adapt to their user needs. Then make it optional. Or at least opt-out. Or say that if you don't enable telemetry, your opinion won't count. Or at least tell you what they're getting and how.
> but no one prevents the developer to keep the dynamic dispatch by default and just do the type-checking, Isn't that what interface{} does?
1. Sometimes being able to ship is more important than being perfect 2. Sometimes I don't care if it's perfect. If I need something for in-house use, Go (and Python) is quite enough for my needs.
>I don't understand people who hate generics. They are just types and they are here to help the developer write compile time type safe code. interface {} everywhere isn't compile time type safe. You're right, and the…
What's the advantage of DDG over StartPage? They both rely on outside sources of data and both anonymize your searches.
>And Android. Android used to honor the promise of being open. Years ago. This was before every manufacturer was encouraged to lock bootloaders, and back when platform SDK's and drivers for hardware were generally…
From a developer's point of view, on one hand, I like this idea. Just about any development environment is better than Android: 1. Callbacks are horrendous. I hate inner classes, they're ugly and unwieldy. I'd honestly…
When this takes off, how hard will it be to install custom roms? One of the great things about Android is that Linux is GPL, so at least the kernel code is open.
> If you do know your compiler and your CPU (singular), you're probably not really programming C. The point is that C is still cleaner than assembly for long programs.
In reality, that's why I think that neither Go nor Rust will ever replace C (Maybe C++, Java or Python), because nothing can replace C. C worked in the 70s, when a naive compiler + asm would work perfectly.
Honestly, Optimizing compilers will kill C. It killed the one thing C was good at - simplicity (you know exactly what happens where, note I'm not saying speed, as C++ can be quite a bit faster than C). Now, due to…
>This comes down to one of the key differences between Linux and BSD: BSD "owns" its userland—the people who develop the kernel, or some system utility, can literally decide to change something, and then do a global…
>The Linux community was way more trying to run on everything. In contrast to some opinions, I like this sometimes. For example, would the world come to an end if FreeBSD came with neovim? If the prompt out of the box…
>Debian doesn't always just work, because a lot of packages are very old. If you need new packages, you don't run stable. You run stable if you need things, well, stable and "just works".
>you can easily run your own pkg repository with binaries compiled for multiple architectures (with build enviroments isolated with "jail") and providing the full range of compilation customization included in the ports…
That's the FreeBSD line, but I don't think it's so simple. The lawsuit ended in 1994. That was before RedHat, and one year into Debian. At that time, the majority of Unixen were proprietary, so if you wanted your…
In my opinion (mostly Debian user with a bit of FreeBSD playing), people use Debian as a server for the same reason a lot of people like MacOS over Linux - It Just Works. 1. For many years, the only way to install…
Can you say that traits are like Go interfaces?
Unfortunately, the problem with Nim (as well as D) is the lack of big player support jump starting public opinion. Languages are inherently vendor-locked* (There isn't any way to foolproofly translate code from language…
>I prefer a nicely sandboxed and secured EME plugin over the insecure and clunkly silverlight pipelight trickery that was necessary before. What's the difference between the two? Why do you think the EME plugin is any…
What about prgmr?
>data on which they (should) adapt to their user needs. Then make it optional. Or at least opt-out. Or say that if you don't enable telemetry, your opinion won't count. Or at least tell you what they're getting and how.
> but no one prevents the developer to keep the dynamic dispatch by default and just do the type-checking, Isn't that what interface{} does?
1. Sometimes being able to ship is more important than being perfect 2. Sometimes I don't care if it's perfect. If I need something for in-house use, Go (and Python) is quite enough for my needs.
>I don't understand people who hate generics. They are just types and they are here to help the developer write compile time type safe code. interface {} everywhere isn't compile time type safe. You're right, and the…
What's the advantage of DDG over StartPage? They both rely on outside sources of data and both anonymize your searches.
>And Android. Android used to honor the promise of being open. Years ago. This was before every manufacturer was encouraged to lock bootloaders, and back when platform SDK's and drivers for hardware were generally…
From a developer's point of view, on one hand, I like this idea. Just about any development environment is better than Android: 1. Callbacks are horrendous. I hate inner classes, they're ugly and unwieldy. I'd honestly…
When this takes off, how hard will it be to install custom roms? One of the great things about Android is that Linux is GPL, so at least the kernel code is open.
> If you do know your compiler and your CPU (singular), you're probably not really programming C. The point is that C is still cleaner than assembly for long programs.
In reality, that's why I think that neither Go nor Rust will ever replace C (Maybe C++, Java or Python), because nothing can replace C. C worked in the 70s, when a naive compiler + asm would work perfectly.
Honestly, Optimizing compilers will kill C. It killed the one thing C was good at - simplicity (you know exactly what happens where, note I'm not saying speed, as C++ can be quite a bit faster than C). Now, due to…
>This comes down to one of the key differences between Linux and BSD: BSD "owns" its userland—the people who develop the kernel, or some system utility, can literally decide to change something, and then do a global…
>The Linux community was way more trying to run on everything. In contrast to some opinions, I like this sometimes. For example, would the world come to an end if FreeBSD came with neovim? If the prompt out of the box…
>Debian doesn't always just work, because a lot of packages are very old. If you need new packages, you don't run stable. You run stable if you need things, well, stable and "just works".
>you can easily run your own pkg repository with binaries compiled for multiple architectures (with build enviroments isolated with "jail") and providing the full range of compilation customization included in the ports…
That's the FreeBSD line, but I don't think it's so simple. The lawsuit ended in 1994. That was before RedHat, and one year into Debian. At that time, the majority of Unixen were proprietary, so if you wanted your…
In my opinion (mostly Debian user with a bit of FreeBSD playing), people use Debian as a server for the same reason a lot of people like MacOS over Linux - It Just Works. 1. For many years, the only way to install…
Can you say that traits are like Go interfaces?