75 karma · joined May 13, 2023
The "64-bit version of x86" is actually the new ISA created by AMD that was backwards compatible with x86 and added a 64-bit mode.
I'm sure that you agree that the company that creates a ISA has the right to name it.
I'm seeing poorly advised commenters in this thread trying to argue that reinventing the wheel is simpler than just using industry standards that are readily available and "just work".
Can you explain in your own words why supporting the world's leading package manager system makes Deno "drop what makes it special"? Does it make any sense to argue against gaining access to all conceivable dependencies?
I don't see where there's any ambiguity on this issue. Each individual has the right to not be subjected to spying and monitoring, which includes collecting personal and private information. A social graph is not a data dump where you are a mere drop in the ocean. A social graph is an ocean of personal and private data collected from you. Therefore, it's quite obvious that individuals have the right to not have all this ocean of personal and private data collected on them, specially without their explicit and informed consent, and they should have the right to force anyone to delete this info, both all or subsets, automatically and reliable and verifiably.
Just because I don't mind hearing what my aunt has to say about what she baked or who she chatted with, that does not grant you the right to get my credit score or where I went to highschool with or who I met years ago or where I lived, just because third parties and other edge nodes in a social graph posted that information and data that enabled you to piece it together. What is there to be discussed?
What leads you to believe that just because you disagree with something then it's automatically a dogma and bad? If you're trying to debate the merits of an idea and you start your argument by dismissing and discrediting proponents, regardless of what they might say or how weak your points are, and to make matters worse you admit the proponents of said idea invariably win over your arguments, doesn't that suggest that there's some likelihood you're in the wrong?
What leads you to believe that "pure Agile is also a fictitious goal"? Unless you're using weasel words to refer to Agile in a way you can cherry pick claims to argue that practices that work aren't Agile because they are not "pure", Agile is ubiquitous and is used in countless success stories.
I see it as adding a solution to a blog post describing the perception of a problem.
Isn't there a catchphrase of sorts that reads something like "either change company culture or change company"? If you can't change the company culture and you feel strongly about that, why do you think it's not in your best interest to change your life for the better? Sometimes you and your job are a bad fit, and there is no way around it.
I wouldn't read too much into it. At best the author is just venting steam, and at worst he's complaining about things he doesn't quite understand. The blog post reads like a rant to get things out of the author's chest without much care on coherence or intent to express well founded opinions.
Sometimes stuff that random people say online is just that.
If you're asking questions that are answered in the article then that means you're discussing things without any context or insight or understanding, and have no intention to gather that context or insight or understanding. You aren't asking questions in good faith if you purposely avoid the answers.
According to caniuse, promises are supported by Chrome since v33, by Edge since v12, by Firefox since v29, and by Safari since 7.1.
Both Chrome 33 and Firefox 29 were released in 2014.
If you put together a shell script that calls some other program that runs a build, that doesn't make shell script a build system.
> The fact that it will run e.g. ninja or make under-the-hood can be ignored for many use-cases.
You can't, though. Some features are only available on projects generaded by cmake for specific build systems.
Make is a part of UNIX, so it's ubiquitous, stable, and time-proof.
If you really feel that way then you will have to ask the OpenGroup people to fix the UNIX Shell and Utilities part, because they seem to have included a specification of make.
https://pubs.opengroup.org/onlinepubs/009695299/utilities/ma...
> For starters, which make?
The interface specified in the standard.
> GNU and BSD are common variants, and aren't 100% compatible.
Irrelevant. UNIX specifies an interface. It matters nothing if some implementation added their extensions.
> For my uses, make offers nothing of value (...)
That's perfectly fine. Just install just in your machines and work on your personal projects as you see fit.
If on the other hand you intend to distribute something you work on, using make ensures that those using specific target platforms don't need to install extra software because it already ships preinstalled.
Make is a part of UNIX, which ensures it is extremely stable and is available on all UNIX systems. You don't get that from justfiles. You get syntactic sugar, but all the best parts of Make are thrown out of the window.
From the article:
> Popular C/C++ alternative build systems are SCons, CMake, Bazel, and Ninja.
CMake is not a build system. It's a build system generator. A higher level abstraction over the problem of specifying projects, which greatly simplifies the work of creating and maintaining them. Once a CMake project is created, it is then used to create the actually build system. Originally it was mainly Makefile, but nowadays it also supports Ninja, Xcode, and Visual Studio. I'm sure that if there is any interest cmake could also be updated to generate other build systems.
You're missing the whole point.
As per the C standard, NULL is an implementation-defined null Pointer constant.
Macros are resolved in the preprocessing step. The compiler does not know what a macro is. What the compiler knows is whatever the preprocessor passes off in place of the macro. This means the compiler only sees a constant, and has no way to tell what that constant means.
If instead of passing random pointer constants you pass an actual type, now the compiler can tell more things.
> If NULL had been (...)
Irrelevant. The whole point is that it wasn't the committee looked at the problem, and it determined that using a dedicated type is safer, more powerful, and more elegant than passing magic numbers around.
Yes, it does.
> If you're programming in C, you usually define 0 as an invalid value, or a null value.
That was also the usual pattern in C++ when there was no alternative. Once nullptr was introduced in C++, NULL or 0 quickly became a code smell.
> C doesn't have the insane type system C++ has and doesn't have a very strong need to make a distinction between a pointer or an integer, since they're all in the end numbers.
C++'s type system is far from insane. It's actually one of it's killer features.
You're both entirely oblivious to the need to not conflate pointers with integers and failing to present any case in favour of the legacy and broken use of NULL, and in the process failing to address all family of known error patterns involving it.
> The printf example you gave is an example of garbage in, garbage out. If NULL is a macro not defined as a pointer sized integer, then you're at fault here.
Again, you seem to be completely oblivious to the problem domain. NULL is not a macro as far as C or C++ compilers are concerned. NULL is a magic constant that's resolved at preprocessing time. Replacing NULL with nullptr means a magic constant is replaced by a concrete type, and thus whole family of errors can be avoided with compile time checks. Claiming that the developers who wrote in bugs are at fault for inadvertently adding bugs makes no sense at all because it does not solve any problem at all, and instead is just cynical finger pointing. I take compile-time checks over unhelpful finger pointing all day every day.
A quarter of all US newspapers closed since 2005, and they've been shutting down at a pace of 2 newspapers per week.
https://www.nytimes.com/2022/06/29/business/media/local-news...
The same source extrapolates that a third of all US newspapers is set to close by 2025.
Do you honestly believe that this bankruptcy wave only affects "woke" newspapers?
Also, your "Get woke, go broke" comment is based on the idea that if a newspaper you follow starts reporting things you don't like or personally agree them protest is a healthy or desirable course of action, as if depriving funds from a business will eliminate things you don't like or understand. I'm not sure this is a healthy take, and is reminiscente of extremism.
Over the past two decades, the number of gyms and fitness centers saw exponential growth to the point where they became ubiquitous, and some workout programs became widely recognized memes. Working out is now socially acceptable, and in some places social pressure tilted to the targeted against those who do not exercise.
Even though diet/exercise changes may not be widely followed, don't you agree that they have been widely adopted?
just-js holds spot 5 of TechEmpower web framework benchmark round 21.
I'm rocking a two node cluster in Hetzner. One is an old 1vCPU small that costs over $3/month, and the other is a new 2vCPU addition that is a dash over $4.
I pay for two ipv4 external IPs which costs more.
Also, Hetzner started to offer ARM64 nodes that are even cheaper.
Yes, Pinggy Pro is more expensive than operating your own nodes in Hetzner.
What I hate the most about today's internet is how search engines allow blatant scrapers to feature so high in search results. So many times I Google for something to find Stack Overflow as the main search hits, and right next to it there are a couple of sites that copied Stack Overflow's questions verbatim. Once I googled for FLOSS projects I had on GitHub and lo and behold there were half a dozen obscure sites that also claim to host my project, with everything copied verbatim from git repo to project descriptions.