My experience with the OrangePi 4 LTS has been poor, and I'm unwilling to purchase more of their hardware. Mine is now running Armbian because I didn't care for the instability, or for the Chinese repos.
They seem uninterested in trying to get their hardware supported by submitting their patches for inclusion in the Linux kernel, and popular distros. Instead, you have to trust their repos (based in PRC).
I don't know what you think "typical Foss projects" are but in my experience they are exactly like your systemd example: one person that does what they want and share it with the world. The rest of your argument doesn't really make any sense with that in mind.
And ~90% of google searches now gives you 10 videos as answers to any query rather than just the web pages that have been turned into videos because youtube makes them more money than regular ads. Assholes.
That is no longer true! You can do it in CSS with a combination of `@starting-style` and `transition-behavior: allow-discrete`. [1]
Another gotcha you'll run into is animating the height. A couple other new features (`interpolate-size: allow-keywords` and `::details-content`) will let you get around that. [2]
They're wrong on multiple fronts, they're regressive. The poor bear the brunt of them.
Despite the bad press, a well run government highway is much cheaper, generally 30% or more of that toll goes directly to maintaining the system and it's profits, there's more efficient funding methods out there.
They're natural monopolies, they fill up with traffic regardless of how much you rip people off.
CSS rules for printing is one of my favorite features of the web. You get a powerful typesetter directly in your browser. For those wondering how it's done, I wrote about it [0] recently for my friends who frequently asked how I generated PDFs for my blogs.
> Should it be illegal to fire employees that recent took mental health leave?
In civilized countries it is illegal to fire someone on sick leave, and I highly doubt you’d get a permit to fire someone who just got back from sick leave.
The review shows ARM64 software support is still painful vs x86. For $200 for the 16gb model, this is the price point where you could just get an Intel N150 mini PC in the same form factor. And those usually come with cases. They also tend to pull 5-8w at idle, while this is 15w. Cool if you really want ARM64, but at this end of the performance spectrum, why not stick with the x86 stack where everything just works a lot easier?
I'll always upvote a recommendation for Amusing Ourselves to Death. I haven't yet gone back to Understanding Media directly yet.
I haven't watched the news in 5 years. I started watching it again since Bondi (I live nearby), and while I'm surprised at the variation in reporting styles (political bias?) between Australian channels, my overwhelming observation has been just how little key information is actually conveyed.
I've found it very helpful to watch the live briefings, Q&As, etc with politicians, but the news cycle here is so short (hourly) that a few minutes later you get to hear a "recap" by the news reporter that glosses over most of the important and interesting points (at best) or actively removes key nuance and outright changes the message delivered by the original person (at worst).
I feel there has to be something between "I heard about a thing 7th-hand" and "I actively watch political discourse / read scientific papers", but I'm no longer sure The News, as we currently know it, is it.
Presumably this was what "journalism" was originally supposed to be.
Not a mobile issue. I am on desktop and had no idea what this service was because nothing on the initial UI explained what we were looking at. I went and double-checked when people here were talking about pricing and VMs. From the home page, I figured it was some text-based game or experiment and closed the page.
It looks like some people who work there are watching this thread, so to them I say: You have got to explain what this is, not just say "the disk persists..." and expect people to dig deeper. Most aren't that curious.
I have mixed feelings about this. On the one hand, I agree: text is infinitely versatile, indexable, durable, etc. But, after discovering Bret Victor's work[1], and thinking about how I learned piano, I've also started to see a lot of the limitations of text. When I learned piano, I always had a live feedback loop: play a note, and hear how it sounds, and every week I had a teacher coach me. This is a completely different way to learn a skill, and something that doesn't work well with text.
Bret Victor's point is why is this not also the approach we use for other topics, like engineering? There are many people who do not have a strong symbolic intuition, and so being able to tap into their (and our) other intuitions is a very powerful tool to increase efficiency of communication. More and more, I have found myself in this alternate philosophy of education and knowledge transmission. There are certainly limits—and text isn't going anywhere, but I think there's still a lot more to discover and try.
Read "the terrifying art of finding customers" by Collin Stewart
Very few know more about outbound than he does, and that book is recent.
My two cents: It's unlikely you can make outbound work for a custom software dev studio unless you go extremely niche and have a way to target customers with relevant needs. The more broad your services the more new business depends on trust, and outbound has the lowest trust context of all top of funnel sources. What works best for dev shops is word of mouth.
Maybe consider a referral program.
Anything that can greatly boost trust when prospects learn about you.
This was a really interesting read. I'd highly recommend it for anybody who's setting up (or currently maintains) a pre-commit workflow for their developers.
I want to add one other note: in any large organization, some developers will use tools in ways nobody can predict. This includes Git. Don't try to force any particular workflow, including mandatory or automatically-enabled hooks.
Instead, put what you want in an optional pre-push hook and also put it into an early CI/CD step for your pull request checker. You'll get the same end result but your fussiest developers will be happier.
The author seems like a nice guy, but perhaps a bit naive regarding the efforts big tech companies go to to crush employees (https://en.wikipedia.org/wiki/High-Tech_Employee_Antitrust_L...). They appear to be a staff level engineer at a big tech company - I don't know how much money they make, but I suspect it's an ungodly amount.
The organisation he works for is implicated in surveillance, monopoly exploitation, and current military action involving particularly unpopular wars. No one forced him into this role - he could have made less money elsewhere but decided not to. He has decided to be a cog in a larger, poorly functioning machine, and is handsomely rewarded for it. This sacrifice is, for many, a worthwhile trade.
If you don't want to engage with the moral ramifications of your profession, you are generally socially allowed to do so, provided the profession is above board. Unfortunately, you cannot then write a post trying to defend your position, saying that what I do is good, actually, meanwhile cashing your high 6-7 figure check. This is incoherent.
It is financially profitable to be a political actor within a decaying monopolist apparatus, but I don't need to accept that it's also a pathway to a well-lived life.
This behavior is extremely damaging to the startup scene. Who would join a startup these days unless it’s run by a close friend or relative? At least in that case, the scorned junior employees would have social recourse.
There are a lot of people hacking on insulin pumps and they are lightyears ahead of commerce. If you want a very interesting rabbit hole to dive into try 'artificial pancreas hacking' as google feed.
I would trust the people that hack on these systems to be even more motivated than the manufacturers to make sure they don't fuck up, it's the equivalent of flying a plane you built yourself.
I publish into an open sea and hear nothing in reply. The constant reassurance from every platform that i use that i am merely "one more post" away from all my wildest dreams has to be true eventually, right?
Any license that discriminates based on use case would not qualify as open source under the Open Source Initiative definition, nor as free software under the FSF definition. You also shouldn't expect for your project/code to be reused by or incorporated into any free or open-source projects, since your license would be incompatible.
You can release software under whatever license you want, though whether any restriction would be legally enforceable is another matter.
> They believe those platforms are "public spaces" while they truly are "private spaces trying to destroy all other public spaces in order to get a monopoly."
The key part IMO is buried in the article - there happened to be an existing, perfectly accurate database containing all the required info about each employee - the same info that previously had to be manually found for each retirement.
Without this, this effort would not have been possible.
> Fortunately, we stumbled on a critical clue. While poring over old documentation, we discovered that OPM actually had data warehouses that stored historic information about every federal employee. Apparently, these warehouses were created as part of a modernization effort in 2007, and HR and payroll offices all across government have supposedly been regularly reporting into it.
> For some reason however, this was not well known at OPM, and those that knew about it didn’t know what data it held, nor considered how it could be used to simplify retirement processing. Not many had seen the data, and administrators were initially resistant to sharing access.
> From a software perspective, this was the holy grail: a single source of truth that held all the information that the manual redundant steps were meant to review. Because the information was regularly reported by HR and payroll, by the time an employee retired, OPM should already have everything needed to process the retirement, without anyone re-entering or re-verifying information.
They seem uninterested in trying to get their hardware supported by submitting their patches for inclusion in the Linux kernel, and popular distros. Instead, you have to trust their repos (based in PRC).