It is less simple, but nowhere Jira-level, and yet still more useful (for my team and I).
We've been using GH Projects at my current org and program for two years. The one feature I wish it had was nested issues.
In Jira, you had Epic > Task > Sub-task and that's it. With GH, you can just have issue > issue > issue (insert "it's turtles/issues all the day down meme"). So it's more powerful, but can be ignored by folks who don't want to do this.
You jest, but I tested this and it turns out that it was JavaScript, not slow networking, that made Jira so slow for me. (I was trying to figure out how to locally cache assets to speed it up.)
The M-series single-core speeds were so much faster than Intel at the time that it was noticeably faster.
Speed is nearly everything and controlling (ie. reducing) speed should be the primary way to influence fatality rates.
Having lived in both Toronto and SF, both cities with 4-way stop and controlled lights intersections.
I'll take 4-way stop any day since speeds are lower. Much better to get hit by a car at near zero speed than a right or left turning car at higher speed. Which is probably why Toronto doesn't have a category for four way stop fatalities.
(The worst are SF's 2-way stops at intersections between equally-sized roads that show up randomly throughout Sunset. Worst of both worlds.)
A municipality could (and should) add speed bumps or other traffic-calming measures even at the approach the light-controlled crossing where pedestrians are often present.
> (The worst are SF's 2-way stops at intersections between equally-sized roads that show up randomly throughout Sunset. Worst of both worlds.)
As a cyclist, I've been yelled at by drivers for not stopping at that type of intersection, where they have a stop sign and I don't. People are working off of their personal version of the rules of the road, where they are always right.
> (The worst are SF's 2-way stops at intersections between equally-sized roads that show up randomly throughout Sunset. Worst of both worlds.)
If you think that's bad, Seattle has 0-way stops at intersections in residential. AFAIK, the rule is if you have a stop sign, you must stop; if you don't have a stop sign and other directions do, you have right of way and should proceed if safe; if you don't have a stop sign and neither does anyone else, treat it as an all-way stop. But from my observations, common behavior is to make it through the intersection about half way before realizing there are no stop signs and then just continue through because what else can you do at that point?
Growing up celebrating Xmas in Canada resulted in me dreading the month before with Xmas music and decorations everywhere. As an adult I love that I can mostly choose not to celebrate (aside from parents and inlaws). Even living in Korea I avoided the celebrations but couldn’t avoid the decorations.
But I do really enjoy one single thing about the holidays: the VLC icon getting a Santa hat a couple of weeks before Dec 25.
VLC has been doing this as long as I can remember (earlier than 2005?) and it’s literally the one thing I look forward to for the holidays.
I found this out in October when trying to figure out this complaint.
timcappalli from FIDO Alliance mentioned in that above thread that plain text exports shouldn't be allowed, and that password managers/providers should be blocked if they implement plain text export.
Since that thread, there's a new spec that allows users to securely migrate passkeys from one provider to another, but no way to export to plain text (for debug purposes, or if there's a bug in the export/import and you need to troubleshoot, etc).
For me, threatening to block providers for implementing a feature that I desire is a great way for me to lose all interest in passkeys completely. I don't trust FIDO Alliance to make the right call nor do I trust big tech companies to produce bug-free software.
Province of Ontario literally just passed a bill (212) to rip up already-installed bike lanes in City of Toronto at an estimated taxpayer cost of ~$50MCAD, despite opposition from city residents AND city officials, which is unheard of because municipal infrastructure is outside the scope of the province.
I've been using data-only plans since 2015 combined with voip.ms VoIP numbers (for Toronto and SF). This means I could travel and pop in a prepaid SIM card whenever I went anywhere and not have any problems using data-based messaging services (Signal/WhatsApp/iMessage).
As of this year I ditched my T-Mobile prepaid data SIM and exclusively use prepaid eSIMs (esimdb.com has a great comparison, but Nomad makes it very easy with their app). So I still have to "swap sims" but it's all done on the iPhone itself, no need to bring a sim ejector/paperclip.
What's really funny is that last week my eSIM ran out (I forgot to top up) and my 16 Pro connected to the satellite network (since it assumed no service was available I guess?), where I was able to use iMessage (in the limited way (to individuals, not groups)).
How exactly are you using iMessage with your VoIP number? I thought it requires a valid SIM card to register the number. Also, aren't SMS, MMS media, and MMS groups super finicky with VoIP services?
Just calling out the poor way this (and many) articles write about car accidents. I’m not a Tesla fan at all but blaming Tesla for the crash is incorrect.
(It is correct to blame them for the way the door locks work though and therefore can be blamed for the excess injuries/deaths that result from the design decision.)
From the article:
> Four people were killed in a fire after a Tesla Model Y lost control and hit a pillar in Toronto last month.
> Five people were trapped inside a Tesla Model Y after it crashed and burst into flames
The Tesla didn’t lose control, the human driver lost control of the vehicle.
From a previous article the day after:
> Police said the driver of the Tesla lost control of the vehicle while travelling at a high rate of speed and collided with a guard rail. The vehicle then struck a concrete pillar, they said, before bursting into flames.
If it wasn’t for the irresponsible driving on the part of the human driver, this incident wouldn’t have occurred in the first place. The driver paid for this with their and others’ lives.
>It is correct to blame them for the way the door locks work though and therefore can be blamed for the excess injuries/deaths that result from the design decision.
This is what is being discussed here: that four people burned to death because they were unable to exit the vehicle.
It's not entirely fair to say it happened in a vacuum, either, since car doors are damaged and fail-shut enough that almost every fire department has hydraulic rescue tools to force open trapped cars.
The spontaneous combustion of Tesla's battery pack was the proximal cause of death here, but that's an EV problem in general, and will probably only grow as they take over the car market.
Maybe we need the car version of https://en.wikipedia.org/wiki/SUBSAFE to account for EV combustion risks that prevent FDs from responding in time for locked doors.
It's not correct to blame them for the way the door locks work. This is the case on all electronic door handles, now becoming common on new cars. The reason you can't have an emergency manual override easily accessible is that a child could use it when child lock is enabled. The US government created this problem.
That is incorrect. This is not the only legal way to design this.
I own a Volkswagen ID.4, also an EV with electronic door handles. The door handles also function as the mechanical emergency release. When the handle is only slightly pulled, the electronic release opens the door. When the handle is fully pulled twice, the mechanical release opens the door. The car also has (electronic) child safety locks, and is legally sold in the US.
Just calling out the poor way this (and many) articles write about car accidents. I’m not a Tesla fan at all but blaming Tesla for the crash is incorrect.
(It is correct to blame them for the way the door locks work though and therefore can be blamed for the excess injuries/deaths that result from the design decision.)
From the article:
> Four people were killed in a fire after a Tesla Model Y lost control and hit a pillar in Toronto last month.
> Five people were trapped inside a Tesla Model Y after it crashed and burst into flames
The Tesla didn’t lose control, the human driver lost control of the vehicle.
From a previous article the day after:
> Police said the driver of the Tesla lost control of the vehicle while travelling at a high rate of speed and collided with a guard rail. The vehicle then struck a concrete pillar, they said, before bursting into flames.
If it wasn’t for the irresponsible driving on the part of the human driver, this incident wouldn’t have occurred in the first place. The driver paid for this with their and others’ lives.
We've been using GH Projects at my current org and program for two years. The one feature I wish it had was nested issues.
In Jira, you had Epic > Task > Sub-task and that's it. With GH, you can just have issue > issue > issue (insert "it's turtles/issues all the day down meme"). So it's more powerful, but can be ignored by folks who don't want to do this.