How many times is this going to get shilled? It shows up at least once a month and the people associated with come in talking like it's almost trivial to "build a better sqlite" or that in essence SQLite3 is "deprecated." Give me a f**ing break.
This is why I keep buying 3B+ and Zero 2 W and not any of the newer versions...it's much more in keeping with the relatively low cost board with GPIO and reasonable compute. It's kind of the last one they made that does what I kind of expected out of a Raspberry Pi at a reasonable price point. If I needed more compute I would have skipped the travesty that is ARM and just bought an x86 system.
Maybe I'm missing something, but the big players that I know ship and sell globally like Digikey, Newark and Arrow are all Adafruit distributors, and presumably that wouldn't change. Do you mean brick and mortar or something else?
Until the FCC wakes up and decides to change any detail of how they certify (which can happen easily), and then everything becomes no longer certified, and you'd basically have a full blanket ban of any transmitter, receiver, esc, motor, completed drone (or anything else that even incidentally emits EMI) that wasn't built in the US. The cards are set up there that it's extremely easy for them to just "incidentally" change a few things and hey no more drones of almost any sort, or RC planes, or hell parts for a whole lot of things.
Reading through the notice from the FCC, it sure feels like they've also banned a lot of the critical components that go into line of sight RC airplanes. It really sucks, I kind of wonder if this won't crush the hobby and cause a lot vendors like Horizon or Hobby King to go under if they can't bring in planes or parts. Maybe they think someone is going to do a terrorism with their foamie Crack Yak or Turbo Timber..
I have worked on several codebases where it was enforced that the commit be rebased off of whatever the main branch was, all units of work squashed to a single commit, and only "working" code be checked into the main branch. This gives you a really good linear history, and when you're disciplined about writing good final commit messages and tagging them to a ticket, it means bisecting to find challenging bugs later becomes tractable, as each commit nominally should work and should be ready to deploy for testing. I've personally solved a number of challenging regressions this way.
I think one should be allowed to push commits that don't build or pass tests provided a) they are marked as such (so you can skip them sooner when bisecting) and b) the HEAD commit after each push does build and pass tests.
Which is the entire point of it. Why should I look at ten commits when I can look at one and get the same exact data? Why should I pollute my production history for what a is likely a bunch of debugging commits? The branch is a scratchpad, you should feel empowered within your own branch, rebase allows you to be lazy in the development cycle while presenting a nice clean set of changes at the end of it.
Yes! When you are deep in the code, your brain operates in a non-linear way. You try a solution, it breaks a test. You patch the test. You realize the variable name is wrong. You fix a typo.
Without Squash, the main branch history becomes a timeline of your mental struggle.
With Squash, the main branch becomes a catalog of features delivered.
No body needs to take a trip on the struggle bus with me...
You can split your work in multiple commits and at the same time drop/squash debugging or wip changes. The result allows you to go into much better detail than a PR description.
I mean Scala kind of does both (and then some). I'm not sure I would call it an OOP language, but you can sure write the same gross Java enterprise bloatware in Scala too if you want.
Wireguard is cool, but there's some reasons it's worth considering OpenVPN (why I still use OpenVPN anyways). First, OpenVPN has kernel mode now (called DCO, which I think Netgate maybe has upstreamed to FreeBSD); I've found it's performance on hardware with AES-NI on Linux is actually often better than wireguard. Second, there's a lot of quality of life things that just work on OpenVPN that you've got to use a ton of duct tape to make work with Wireguard, a major one being handling DNS record change (think especially dynamic DNS, which is likely if this is IPv4 and a residential connection). This is a huge pain with Wireguard, but just works on OpenVPN. Similarly if you have multiple WAN links, like I do, for OpenVPN it's just two connection stanzas and it largely just works. Again for Wireguard you're adding lots of duct tape to make it work right. I know Wireguard is the new hot thing, but it leaves a lot to be desired in the resiliency and features department.
One of the major advantages for Wireguard over OpenVPN (for me) is that it's quite difficult for random port scans to detect it.
With OpenVPN it's hanging out there responding to everyone that asks nicely that yes, it's OpenVPN.
So anyone with a new exploit for OpenVPN just has to pull up Shodan and now they've got a nice list of targets that likely have access to more private networks.
Wireguard doesn't respond at all unless you've got the right keys.
Also, fwiw - we're approaching 11 years since it was announced, and 5 years since it was accepted into the Linux/BSD kernels.
I use wireguard as my main VPN to connect to my homelab from my phone and my laptops.
I also have an OpenVPN as a backup option, running behind sslh.
My same port on my router (443) serves both a webserver hosting photos, and that OpenVPN instance. This allows me to VPN into my home in most firewalled office networks.
i’m assuming because of the “web server hosting photos”. Probably Immich if i had to guess?
tailscale is fine if you’re somewhat tech savvy, but it’s annoying to show all your friends and family how to “correctly” access your web server. Too much friction. First download the tailscale app, sign in, blah blah. Then you also are unnecessarily bogging down everyone’s smartphone with a wire guard VPN profile which is…undesirable.
I like tailscale and use it for some stuff. But for web servers that i want my whole family (and some friends) to easily access, a traditional setup makes much more sense. The tradeoff is (obviously) a higher security burden. I protect the web apps in my homelab with SSO (OIDC), among other things.
I prefer to gatekeep "entry points" with Tailscale. A server can have HTTP/S exposed to the world, but its SSH can stay behind Tailscale to enable defense in depth.
Keeping Tailscale as the only security layer will be foolish of course, but keeping the entry points hidden from general internet is a useful additional layer, if you ask me.
As a matter of principle, I like keep the number of open ports to a minimum. Let it be SSH or VPN, it doesn't matter. I have been burned enough times.
I've applied the same principal to my network. Though, I do have plans to re-open some additional ports beyond just SSH / VPN.
Thinking through how I would achieve this introduced me to the concept of a DMZ-zone. The DMZ places publicly accessible services in a highly locked down environment.
DMZ is a very old concept, and applying it is easy when everything is in a single room, connected to a single network, and everything can be isolated there.
When the network is distributed on multiple sites, things get exponentially harder if you don't own a dark fiber from site to site and have essentially a single network.
I personally manage enough servers to scratch that itch, so I yearn for simplicity. If Tailscale gives me that isolation for free (which it does), I'd rather use that for my toy network rather than an elaborate multi-site DMZ setup.
OpenVPN is a proper VPN protocol with a serious performance troubles if you misstep even once.
Wireguard fanboys just never use it more than on a couple of devices where they could manually tinker everything what is needed, they never provided a VPN solutions for even dozens of users.
Oral quals were OK and even kind of fun with faculty who I knew and who knew me especially in the context of grad school where it was more a "we know you know this but want to watch you think and haze you a little bit". Having an AI do it's poor simulacrum of this sounds like absolute hell on earth and I can't believe this person thinks it's a good idea.
I remember when everyone was talking how we would all be gig workers and it was going to be the best thing ever. I am eagerly awaiting seeing whose legal department if any poop their pants tomorrow. Maybe if we're lucky we'll even see an 8-K soon.
some countries do a better job of protecting their population from corp psychopath companies.
Australia is one.
but its not enough and the moment the right wing side of Gov gets in they start rolling back a lot of the labor law protections the left wing work at putting in.
> Arguably, the latter isn't really a labor law issue, its an immigration quota issue.
Immigration quotas should probably be considered part of labor laws though, given the impact immigration can have on wages and the job/housing market for natives.
reply