2,165 karma · joined June 5, 2009
http://joekrill.com
Why is that a problem? At this point in the game most things that need to be done to address climate change and pollution are reactionary.
> If this comes down to CO2 there are bigger fish to fry, no?
You can say that about almost anything. There's always "bigger fish to fry", but that doesn't mean we should only ever deal with the "biggest fish". We regulate car emissions even though ships and airplanes are arguably the "bigger fish". We prosecute thefts even though most people would consider prosecuting murders the "bigger fish".
> In 24 hours, the space station makes 16 orbits of Earth, traveling through 16 sunrises and sunsets.
Last weekend I stayed at a Hyatt, and the first thing I did when I got to the room was power it up. But I couldn't for the life of me get the captive portal page to load when I was connected through it. It worked fine connected directly to the hotel's wifi, but through the router - nothing. So I gave up. It wasn't worth the hassle.
There is neither of these, though. There is only people speculating that they MUST be cheating because they didn't behave exactly as they were expected to.
> By your standards I shouldn't be able to speak until we examine the coin directly [...]
I never made any such statement or made and indication of specific "standards".
We should absolutely look at the coin if it's behaving this way. But we can't just conjecture that it must be weighted with zero evidence of that.
That doesn't make it right to accuse people of cheating without any evidence beyond "well a _normal_ person wouldn't have done something like this, so they must be cheating!".
So what? Just because someone has cheated in the past does not in any way prove that they've cheated in this particular case. It only proves they've cheated in the past. Is it suspicious? Sure. But any accusations of cheating are still pure speculation.
> Officials literally found weights inside the fish. Both of those are in this story.
And I specifically mentioned this in my comment.
It looks very similar to the vote rigging claims we're seeing a lot more of recently in the U.S. Don't like the outcome? Just blame your opponent of cheating! No need to show any _real_ proof - just make up some vague claims of what _could_ have happened! And just keep repeating it. And this all seems to working pretty well - THAT is the scary thing
Obviously none of this applies in the case of the fisherman, who seem to have been caught red-handed.
1. Pricing. It was affordable and straight-forward pricing. There wasn't a huge "tier bump" - I think it was like a flat fee per 1000 requests after the free alotment.
2.You always could expect the same response, regardless of location or date. You could get an hourly forecast 3 years into the future, or 20 years in the past. Most other weather API will give you hourly only from "now" into the next few days. Or you can get daily for the next ten days or something like that. So you had to build logic around into your app. With DarkSky I got the same response no matter the day, time, or location. So it was much simpler to deal with.
3. Accuracy. I was always amazed at how accurate it was.
> No location permissions needed to get basic weather data, to reduce location permission use by apps when it's only for weather.
This seems tricky. The response currently returns the latitude/longitude, so it could be a possible way for an app to get around requiring location permissions. Even if they excluded that, there are other data points that could probably help narrow things down, particularly when there is an active weather alert, because those tend to specify locations.
A developer has started an impressive and ambitious project called Pirate Weather, which I planning on using moving forward, for those looking for "drop-in" alternatives: https://pirateweather.net/
What does that really matter, though? You could ask the same of _any_ modern application, NodeJS or otherwise: "On average, how many other organizations & human developers are somehow involved in the dependency graph of a modern application?". Look at your web browser alone. You have an open source rendering engine. The JavaScript engine. The underlying libraries used to handle things like SSL, TCP/IP, DNS lookups. It runs on an OS that likely has layers and layers of open source code. Which runs on hardware from various manufacturers with firmware written by many people spread across many organizations.
And even if you think setting up a "sane development environment" is simple, it gets much more complicated as you add additional languages and versions of those languages, and their underlying frameworks, etc. For example if you look at NodeJS alone: we have things like nvm to switch between Node release versions because you'll often have different projects relying on different versions of Node. Or you could just use Docker and it's baked in, basically.
There is an open-sourced option called GlitchTip (https://glitchtip.com/) that is much simpler to self-host. I believe they forked the Sentry repo before the license change. It's not quite as feature rich but is a pretty great alternative.
I met Natalie and Chris years ago when I interviewed for a position at Wildbit (one I really wasn't qualified for). I'm sure they don't remember me, but I was super impressed with them - their approach to business and respect they had for their employees. At a time when I was becoming disillusioned, they showed me that it was possible for a company to be successful without putting profits above all else, and actually showing compassion for their employees. They were one of the first companies I'd heard of who were actually experimenting with 4-day-work weeks.
I think this mindset is becoming a bit more common today, and will only become more common (maybe that's wishful thinking?) - but I think they were _way_ ahead of the curve.
I don't think it's really a comparable to a voice assistant. It's more "Google Glass" than "Google Assistant".
Or the very real scenario where you've been using a free Google Workspace account (is that what it's called these days) with a custom domain, and suddenly Google wants to start charging you for it. Meanwhile you've "logged in with Google" using that account across many, many sites and Google hasn't offered anyway to migrate away from that. So you either pay up or lose access to any of those accounts.