As an end user, I don't mind if you're building a product with rapidly changing API's out in the open. I'll still use the product if it's useful and deal with the churn. What I DO care about is not having half of that project rug pulled 12 months down the line when your Series B folks decide that this particular money knob needs to be turned up.
So if you want to not piss off your users, that's the way to do it. Build a model where you can actually sustain the product, and no, giving it away on seed and series A round money then rug pulling that gift is not the way to achieve that.
Okay, that’s slightly more reasonable it means if I’m going to be rolling stuff back into OSM in a new country I should at least have a quick chat and ensure what I’m doing abides by that country’s regulations etc like South Korea has some notorious law around data residency
SDET is one of those things that you can never justify, but if you allow it to happen and the SDET is good it pays itself off several hundred times over
If you’re a layman investor just dump all of your shit in index funds. Even if you’re smart and sophisticated, you’re still competing against the massive amount of fraudulent insider trading happening right now with zero enforcement and are trading at a disadvantage as a result
I think the situation is slightly more nuanced than that. When the easiest path by far is long lived keys, there is something to be said about the security posture of a solution where those are the default behavior, especially if they don’t actively discourage usage in documentation. For instance if you go to aws and try to create an iam user with access key/secret key they warn the shit out of you multiple times. They say things like “this is a bad idea” “we don’t recommend this” and “use this better solution instead”. I think if you’re providing an auth service like this you have some level of responsibility to guide people towards the less naive solution - part of what you’re selling in an auth offering is security, so if you default to garbage security, you don’t have a very good offering
Ah, the starry eyed lifecycle of project management. Every young project management tool, born out of the same concept of feeling like its predecessors were too complex. Next comes the growth and excitement phase. Then the new feature requests come in. Now I’ve got a few users, and they are requesting things that expand the scope a bit. Fast forward 5 years and a couple funding rounds and we are now a scrappy PM startup, still slim but growing and can do a lot more. Fast forward 5-10 more years and we have pivoted to enterprise, implemented every feature under the sun and completed our transformation into the Jira operating system
I’ll just say as nix Darwin user the default vanilla install does not garbage collect well and every 2 months or so I have to hack around nuking shit in my system to free up space. Maybe NixOS itself is better managed and it’s an idiosyncrasy of nix-Darwin. Maybe not
Agree but I think it’s interesting to discuss the larger implication here. Nix the language and ecosystem has historically been completely unapproachable for people unwilling to beat their head against the wall continuously to figure it out. It is famously unapproachable. Now, the benefits are accessible to the quasi-layman. Good news all around
I mean, just the way Tao phrases these inqueries seems to imply a weighting towards an extremely abstract and high level rigorous corpus. In a way, prompt engineering really is the big unlock here.
1 year ago everyone would have called you insane for suggesting this. Now we all shrug and say yeah maybe we can do this and it’s actually a good idea?
I’ll go ahead and post the obligatory comment about how it’s a bit ridiculous that they didn’t include in the spec an easy way to quickly visually identify the capabilities of the cable (data vs power etc). Single biggest flaw of the spec in my opinion
You will never find anyone who is against these cameras saying that they don’t reduce crime. Of course they do. The problem is what you give up to have that is far, far more valuable and we can point to the “Ben Franklin” quote here about those who would give up freedom for safety deserve neither.
So the argument here is that people are too stupid to realize that they are being manipulated into being controlled, therefore it’s ok?
Sit someone down, a normal average person, and explain to them the actual implications and then do you think they will agree? Reality shows that when people actually understand what surveillance means they reject it wholeheartedly
The thing is I think if you give people the choice between a 0.001% chance of getting murdered on the street or a 100% chance of being surveilled 24/7 you will find that people will take their chances with the murderers
Interesting, I get occasional glitches, mainly around placement of the text bar, but they are visual and don’t affect behavior. I’ve been living on the browser on iOS for about a year now and I enjoy it.
I did eventually have to abandon the desktop one about a year ago though due to bugs. It seems like it’s better now though.
I don’t think so. The colloquial usage exists as grandparent commenter describes. I can be a “songwriter” without literally writing the lyrics to my song down.
curious how hard it is to implement wire protocol compatibility vs the internal api surface. Are we talking like, an order of magnitude more work here? I wonder if, for example, Aurora team are literally maintaining forks of extensions for their implementation and that's why only a subset of all possible extensions are supported?
Supporting Postgres is a good goal but honestly the real challenge is extensions. Would supporting Postgres wire compatibility guarantee any Postgres extension would also work? This is one of the problems with Aurora - it’s all well and good until you need an extension that isn’t on the blessed list