firstalert acquired luma, which had acquired birdi, which was kickstarter campaign smart smoke thing, which shipped nothing to most of kickstarter backers
some m&a execs clearly did not have good vaporware detector there!!
I’d imagine it has to be a regulatory nightmare. There’s really no options on the market. First alert at this point just has the zwave one that can’t be hardwired or interconnected so it’s not to code in many locales. Nest is pretty good but it won’t work intranet only and that’s a dealbreaker for me; I do iot but it has to be gear that can cope with being on a vlan with no internet access. The only other options are sketchy brands that don’t give a fuck about us regulations. Sometimes it’s a chinese company that has some staying power like xiaomi but sometimes it’s one of those random ones that likely won’t exist in 2 years
A shame because I would really like to be notified if my house is burning down while I’m away from it. Would be pretty handy.
youtube migrated away from vitess several years ago
Mysql product is circling drain under oracles direction anymore. New 8.x “innovation” releases lack any important features. even Mariadb is out executing oracle despite being broke!
Mysql community is in bad shape too. Official slack channel is avalanche of lazy newbie questions. Official linkedin group is endless spew of “learn sql cheat sheet”
Sad. It’s done for. community may still be “enormous” but that is bad thing when its communication channels overrun by sub-bootcamp-level devs
I'll believe it when I see it. Millions of applications use MySQL, and Vitess has only matured and grown.
They said Java was done like five times. It's in the midst of another massive revival. I think the bet on MySQL is a solid one, and I think reasonable minds should be able to differ about this, so I can't bring myself to be as sure as you seem to be.
I can say this: Our app, built on Planetscale and MySQL's protocol, has been fantastic to work with. We run locally against MySQL and H2, and in prod against Planetscale. Everything works really well. Boost, replication, backups, branching, etc etc. We use all of them. Every feature works great, does exactly what it says on the tin. We have never had a single problem.
So, in theory, yes, these things are all on a timeline of some kind between life and death, but I find it very hard to believe MySQL or Vitess are near the end of theirs.
I don't really recall because I don't think our database has needed much on top of stock MySQL. Maybe JSON columns? I don't really care. Just being candid as a user; it has not worried me, no.
innodb supports cross-schema foreign keys, there’s no limitation to tables in a single database
can be terrible in mysql 8 though due to metadata locks now extending across foreign key boundaries. this means alter in one schema can block things in other schema if foreign key across databases
speaking of, am surprised that blog post author doesnt discuss the new mysql 8 metadata locking behavior, is new major problem with mysql foreign keys!
only oracle knows. and they don’t share answer yet, on this site or any other
only public news so far is extremely brief twitter mention of future switch to separate LTS releases from feature releases
big picture, hard to see what would motivate them to major re-invest in current mysql product model! amazon, planetscale, and co all profit off of oracle’s mysql server development efforts. and oracle does not get anything in return
assume this why more and more mysql dev efforts go to saas-only product like “mysql heatwave”!
> why always repeatedly write the same comment about not going “all in on github” in these threads? what is goal of writing this hundred+ times?
Because I can. How many more times does a service need to go down in less than a month to deem it unacceptable for any use? Unless you think paying for downtime is acceptable?
> i dislike github quite alot but this does not achieve anything.
That is not my problem since I saw the problem years ago and chose to self-host instead. Rather than others complain to GitHub, they might as well self-host instead for reliability.
If you can setup a simple SaaS website, you can easily self-host a Gitlab / Gitea instance for 1 to 5 people. It's not that hard.
> no one else is saying to go all in on github so what is this even reply to?
So you didn't read this then?
>> We're all in on Github actions these days but there was a time when we used to maintain our own Jenkins instance. [0]
>> At this point, our self-hosted CI and code review tooling has had significantly better uptime for the past year. [1]
The schadenfreude for GitHub's unreliability and some of its fans celebrating monthly down time only makes it hilarious to watch.
so, because two people said they go all in on github on an hn thread TWO YEARS AGO , you feel the need to post public i-told-you-so hundreds of times ???!???
i am amazed @dang is ok with that, it seem completely deranged man, borderline harassment
I already gave the solution years ago [0] and each time GitHub goes down, hundreds of comments continue to complain when the solution is right in front of their eyes.
> i am amazed @dang is ok with that, it seem completely deranged man, borderline harassment
What harassment exactly? That whatever helpful advice I said in [0] and not 'centralizing everything to GitHub' seems to have aged well?
There is nothing 'deranged' about explaining preventative solutions like 'self-hosting' to those still using an unreliable service. In fact, it is more 'deranged' to believe that GitHub has gotten any more reliable after Microsoft acquired it.
You can continue to use GitHub's services, but don't complain when something from GitHub goes down again in less than a months time when the solution has been in front of you for years.
Seems like you're the one that is showing signs of 'derangement' and episodes of 'madness'. I'm just laughing at you and also at the ones that still continue to rely on a service that evidently goes down each month with the solution given to them, years ago.
> ok? and who in THIS THREAD is saying anything remotely like that?
Whatever someone said about exactly “all in on github” verbaitim is a 'minute detail' you decided to focus on to deliberately miss the forrest for the trees and to make an excuse for an argument. I also include using any of GitHub's services, which as the evidence suggests is beyond poor and comes with folks here complaining about them. Especially GitHub Actions.
So you attempting to narrow the scope to who said what verbaitim from the start is essentially missing the wider point. In fact, it is a distraction, derailing the general and entire point of GitHub's years of unreliability.
> who are you responding to??!?? comments makes no sense, derangement!!!
So far, you for showing yourself as a prime example fitting the definition of 'derangement' and to everyone else who is complaining about GitHub going down despite its track record, assuming you have read the links. There's no need for you to continue embarrassing yourself here and in your next reply, since you continue screaming and 'shouting' in caps-lock whilst attempting to put forward distractions that fails to address the main issue of GitHub's history of downtime and incidents.
you are spending time creating multi-year linked list of hn comments every single time a website you dislike and dont use goes down
i am “failing to address main issue of github’s downtime history”? indeed sure i am not addressing this, because it is not my care to address! why care when website i dont use and dont like goes down? not my problem!
do you see anyone else on entire hn creating redundant toplevel comments that then link to previous comment on same topic, spanning hundreds of comments across multiple years, all to post told-you-so to some random other commenters from 2-3 years ago? no one else do this, is deranged!
i strongly dislike planetscale and even i think this is not a useful or fair comparison .. sqlite works with local files, much simpler, no network latency, no HA
> i strongly dislike planetscale and even i think this is not a useful or fair comparison .. sqlite works with local files, much simpler, no network latency, no HA
To be fair, if you accomplish the same effect without needing distributed computing, then the solution gets much simpler, you cut out worrying about network latency and HA*
* the probability of node failure grows very rapidly with the number of nodes. Same reason you probably don't need RAID for 1 disk, but you definitely do for a dozen
If you actually crunch the numbers, you'll see that the likelihood of multiple node simultaneous failure of a larger cluster is actually often as high, or higher than the likelihood of a single node failure on a non-distributed application.
Despite running redundant distributed set-ups, services today really don't have particularly spectacular availability. Google, Facebook, Twitter, Github; all go down or brown out frequently.
Yes, the sensible default for this feature would be opt-out, like noatime, in case you need the performance boost and understand the implications of the choice.
firstalert acquired luma, which had acquired birdi, which was kickstarter campaign smart smoke thing, which shipped nothing to most of kickstarter backers
some m&a execs clearly did not have good vaporware detector there!!