291 karma · joined December 28, 2019
Just because you can recompile a kernel following someone else's recipe doesn't mean that you understand how to configure one yourself, much less how it works. Regarding security, just a month ago any Omarchy user who understood how the `docker` group works could escalate to root without a password.
What I'm trying to say is that one cannot buy the technical competence. Working on medium-complexity web apps and doing system development are two very different things. So far, Omarchy has been amateur hour when it comes to the latter.
I would gently disagree. There are hundreds people on reddit who spend inordinate time to rice their desktop and share their dotfiles. They just haven't previously written their name all over a few prominent online projects to then market what they've done as a distro and solicit multimillion dollar donations with a straight face.
It has received a lot of money, way more than necessary to bootstrap development of the actual distro. Making new useful open source tools, hiring developers, engaging in FOSS advocacy are all the things they are not doing nor planning to do.
Instead, they just peddle influence. You pay ~$10k to a popular youtuber to promote your product. Now you can pay more money and your products will be promoted by DHH himself, for longer.
Yeah, right.
> You can certainly ask me to stop showing it to people.
There is much better solution: add author's websites to dnsmasq, so they stop resolving:
http://www.expatsoftware.com/ http://www.expatsoftware.com/articles https://stravaeger.com/ http://www.twiddla.com/ https://www.s3stat.com/
I only wish there was a centralized registry of websites that are controlled by parties that have galavant attitude if not deliberate misunderstanding of what does the right to privacy mean.
There is quite a bit to dig into, according to ChatGPT:
* Unauthorized access to obtain information — § 1030(a)(2)(C)
* Computer fraud — § 1030(a)(4)
* Causing damage to a protected computer — § 1030(a)(5)
* Attempted unauthorized access/computer fraud under 18 U.S.C. §§1030(b) and 1030(a)(2)/(a)(4)
* California §502(c)
* (the list goes on for quite a while)Following your logic, we cannot critique anyone in particular ever. How absurd!
> You're using "professional" to mean "regarding the profession" whereas others are using to mean... you know, the opposite of "unprofessional".
At the end of the day, it is the same thing. Person does what is their job according to common standards.
Andrew runs a software foundation, and it is his job to make sure that behavior of one of related projects does not disrupt the stream of all donations or bury his project under a pile of slop submissions. Highlighting the technical dysfunctions of the other project is an effective way to show the differences between the two. Do you have a suggestion that would be just as effective, while being more "professional"?
On balance, the false sense of security that the automated check would provide might actually be detrimental.
Author wants to hide a horizontal scrollbar. Any junior frontend dev worth their salt will be asking right away "where do I stick `overflow-x: hidden;`?" A complete solution will then require hitting "Inspect element" in the browser to find the CSS class and running (rip)grep to find where it is in code, to then add a single line to.
An actual proactive programmer might start asking more pointed questions like what content does an empty textbox have that it overflows? And why do I need to insert this workaround that treats the symptom and not the root cause in two different places? Isn't it better to style `textarea` once? Etc, etc.
[0] https://github.com/datasette/datasette-agent/commit/a75a8b72...
Now they are snapshotting the bleeding-edge distribution and call it general purpose, which carries a strong implication that it is ready for all kinds of production workloads.
It is not. That is why there is a Fedora/RHEL split in the first place.
> In late November 2023, the city announced that it would shelve the pilot.
I would agree that implications regarding the use of those models do not hold, but not the ones about their quality.
As for the customers, very few of them operate at a scale that requires the monumental amount of engineering required to replicate the whole of AWS with its many dozens of services.
[1] https://www.seattletimes.com/business/amazon/amazon-reports-...
In reality, you can have almost any people and processes. The trick is to put your servers and data in more than one place. If you have uptime of just 99% for a server (~3 days off in a year) and have them in 2 unrelated places, you will get 99.99% uptime. 3 places will give you 6 9's. The only thing that has to be ensured by people and processes is graceful fallback.
Notice how I say uptime and not SLA. SLA just means that you will get a little bit of money back if uptime dips below the SLA level. Oh, and for EC2 it is just 99.95%. So, if you really care about your users, you will engineer your systems to stay up rather than hoping that a third-party provider's SLA will save you.
According to https://typespec.io/docs/standard-library/built-in-data-type...:
* unixTimestamp32, but no 64-bit version
* plainDate that can be "April 10th" without the year
* DefaultKeyVisibility, OmitDefaults.. what?
I am genuinely curious how did that happen. Design by committee? Some secret use cases that leaked into specification?