anuraaga

The shared "w" with Warp triggered some memories. I hope things go better, but after being burned once I don't see myself getting off of p10k ever, possibly for the worse.

Everytime I see a post about Japan here, I search this. It was funny to find this likely GPT-generated result in the first few results.

PS: please delete this account?

This comes after this year selling the rights to the Transformers movie series, an arguably larger hit to their ability to have mainstream impact. It seems very unlikely they wouldn't be looking for a buyer for WotC as well, and trimming down to just the IP may be making it a better sale.

The company is struggling and likely pulling out all the stops the avoid bankruptcy, when you need liquidity this could very much include cuts to otherwise profitable segments.

Just "terrible for desktop". I don't have any data to back it up so take it with a grain of salt, but I suspect for desktop Linux use, Ubuntu is far more prevalent than RHEL, and probably hacker types will otherwise be using Arch. So this change probably really only affects people that should have switched their desktop distro a long time ago.

For server use, where this isn't an issue at all for most use cases, putting aside personal preferences, RHEL is likely not a terrible choice, especially on AWS.

From what I understand, cars in Japan are all capped at 180 km/h, and cars that are capable of more often have a gps check to unlock automatically when on a known race track.

180 is still quite high but at least not completely insane as some of the gangs were before that limit. A number would probably need to be found for any country, state, etc but the tech is probably ready.

I had a similar experience with a Chinese scam seller on eBay with a $500 GPU. tl;dr neither ebay nor PayPal would accept a claim because they had proof of receipt from DHL. Of course, a simple call to DHL could easily verify it was delivery to a different address but even providing an email from DHL to this effect as evidence didn't change the line. Eventually had to charge back and luckily in my case that did go through after about 3 months of process - the phone call from the card company in the process was nice to verify unlike everyone else it did actually get handled by a real person.

Naturally that was the end of my eBay account, PayPal unfortunately I do need from time to time.

I suppose this is just standard practice in the industry but wonder why it can be so consistently bad even with real evidence.

Not sure I quite follow the point, Microsoft maintains PyLance and Pyright, tools that have had a large positive impact on Python development, including AI. Not sure about live share, but if there are feature gaps with paid IDEs I would say they're not so large - the functionality available for free in VSCode or its ecosystem (enabled by Microsoft with the help of many OSS developers) has helped democratize software engineering in a great way.

Yes they have some problems in hiding their attempts for lockin on the Windows side but ignoring all the good and just labeling them terrible for that is troubling.

The article specifically is about AI. Don't most useful LLM models require too much RAM for consumer Nvidia cards and also often need those newer features, making it irrelevant that a G80 could run some sort of cuda code?

I'm not particularly optimistic that ecosystem support will ever pan out for AMD to be viable but this seems to be giving a bit too much credit to Nvidia for democratizing AI development, which is a stretch.

I suspect many developers, including OpenAI engineers are using VSCode, maybe TypeScript for frontend engineers, GitHub for sure which had no real features like pull request approvers before Microsoft money came in. Less at OpenAI most likely, but C# and .NET are going strong with bleeding edge tech like .NET chisel containers support. And I've seen great support from their engineers working on OSS, best of FAANG.

Google created the meme that a company could be evil or not but we're past that age. Let's focus on the experiences, and while not forgetting the past (yes the 90s do not paint MS well), be forgiving. MS seems to continue to develop and even innovate on a lot of this tech, painting them as an evil dinosaur seems frankly ridiculous. Yes as with any large company, there will be parts that are good and parts that are not.

Disclaimer: I have never worked at Microsoft and own no stock directly though so have ETFs. And through OSS I have some friends there that I strongly respect and think are awesome and always think of them any time I see hate talk towards MS, which is unfortunately common...

I think it's closer to 1%. If the average Googler drinks 500 lattes per year on campus, this seems to enable about 5 more off campus.

Most people in jail will have lost much more than just a blog. We really need to have some more perspective here, memories of when sites just disappeared completely all the time may help though.

I have something in Dropbox from many years ago which I don't remember. It tomorrow I found I couldn't login to my account since it was deleted, yes I would wonder what I lost, but I would also acknowledge that I wasn't actually using that data and had some forced spring cleaning. It's ok really.

2 years is a long time to not login to a single Google service given their reach, let alone the one that might have data like Drive. Speaking on principal, not reality , for a free service that costs the end user $0 and the provider >$0 makes absolutely no sense to complain.

Since the post was way too long to be without motives, presumably.

Am I the only one that remembers frequent outages before the acquisition? I didn't keep track in a spreadsheet or anything so don't have any data to back it up though but always assumed it's similar to Twitter of the day, hard to make a stable service in Rails.

If anyone can actually put out the data that would be great. I suspect there was a period post acquisition of relative stability that dulls our memory of frequently broken PRs which we probably just got used to at the time.

I'm assuming they're both VC companies in the same portfolio and are cross-marketing. If not, the the descriptions on both sides seem quite excessive indeed...

It would probably be worth paying/staffing whatever though since people may do something for free, but it may not be enough to make a happy end user.

Not all companies miss this, Amazon has strict SLAs on responding to user requests, and this even includes GitHub issues. Personally, I find it rare, though not non-existent, to have a good experience with Google customer support or OSS while Amazon generally feels pretty good. Maybe just lucky of course but the brand effect is obvious to me and perhaps worth the companies spending a bit on.

Exactly this. There was a time I tried diversifying from mostly FDN (tech only) to include VTI (S&P) to still trend growth. And eventually realizing these indexes are mostly the same, switched the lower-growth side to include VT. But I find even that, while not as much, is still dominated by the same companies. I would say these two are the vanguard of passive investing (pun intended) but are not working as they used to at diversifying. It might not matter though given these big companies seem too big to fail at this point and some growth is still desired, cash doesn't seem far worse than equal weight indexes at least for now.

I suspect everyone is saying the same thing, S&P isn't broken, it's not as diverse as it may have been, but that doesn't mean it's something to avoid when doing passive investing, knowing it's not quite diverse would be a plus though.

YouTube premium allows watching content without ads for a similar price. It's unlikely that they actually stop Google trackers for youtube premium users though so you pay and get no privacy benefit.

Assuming that a different content medium, Facebook actually implements a subscription that removes ads and trackers, that would be a win, wouldn't it?

My running joke is that it would be awesome if Satoshi Nakamoto were North Korean and this was all planned from the start. I'd give it a 10% chance of being the case.

Ko works ok but lacks a lot of configurability, compared to something like jib, that does end up important. There are a few open issues on it but the commit history is basically dependabot, not much action for UX. Better than nothing I guess but it really does give off the feeling of a project spun off from Google to let it die.

Despite that it's probably still the best tool for building containers in Go, but it's not pleasant.

I believe this convention was used widely outside of Rails too so it's less a Rails convention and more a late 90s early 2000s convention. Even now I suspect many articles with good SEO will give table creation SQL using auto increment instead of uuid so maybe just software convention.

It's ok to flag this since it's not related to hacking and otherwise long and boring. Isn't it?

I guess because only the 1/70x configure their c++ toolchain with sanitizers.

Assuming the paper is actually relevant given anyone can post any PDF to hacker news and make it semitruth.

Just for reference I did give it a try

https://github.com/wasilibs/go-zstd

Mostly since I hadn't found `compress` supports zstd. Wazero performed reasonably well against the cgo library but was indeed much slower than this proper pure go port.

AI-specific regulation is needed for the same reasons that crypto related regulation is needed - the tech exists and anyone can do it to do bad things without being tracked. Murder is illegal but if there was a way to commit it without anyone knowing, it would become quite popular.

In terms of deepfakes or crypto scams, in the end what we need it is more literacy on the matter, which won't prevent the ability for AI to do "things" but will let us acknowledge that's where we're at. Specific laws to get everyone on the same page on this is absolutely necessary.

The activity tab not defaulting to unread-only is the most perplexing design in history. Given that the setting is per workspace, you end up switching so many times to avoid a persistent white dot that you just start hating that tab. Ignoring it is an option but "Inbox Zero" type of guys like us just can't I think.

It really feels like the intended usage is to ignore white dots and focus on red, but then we really need a setting to remove all white dots who really can't proceed to real work until they're gone.

In the age of supply chain attack weariness and general risk skyrocketing, it is a bit funny seeing the many observability vendors wanting you to give them kernel mode access. And it's sad that most apps that will be most in need of automatic instrumentation are "frozen" rarely developed / updated apps at critical institutions like banks.

As for the original post, opentelemetry is forced to be relatively slow because of a huge amount of semantic conventions that are meant to make data more useful. I won't go into the legitimacy of that, but while I haven't been able to verify the data this solution records, it is very unlikely to be recording as much information. Manual instrumentation would never loose to eBPF in principle, at least in a compiled language like Go, but eBPF does have great potential to perform better than OTel while recording far less data. Then comes blog post, users giving the keys to their kernel, and data ending up in the hands of an enemy state. I doubt that's the case this time but it's only a matter of time.

Banking apps if you see this, please just instrument your code. Thank you.

Assuming someone actually knows it (most non-engineers will likely install an app not finding one called QR), I find the UX to show a small, non-persistent link hover on top of the code difficult to use compared to a normal qr reader (both built-in or 3rd party) which freezes with a large clickable region when it detects a code. Especially when outside and lighting conditions or angles can make scanning a code a challenge, having to actually click to complete a scan would always be a big problem for me, so eventually I installed a third party app. Finding the built-in "app" was nice to allow uninstalling that.

This may be a more important issue in Japan where I think? QR codes are more used than in the US and often require scanning around other people, or other physical challenges. I guess most here get around the problem by using an iPhone though which has a built in and highly obvious QR app.

For anyone finding the qr reader unselectable for the lock screen buttons, don't forget to first enable it in the quick settings tile.

To anyone that didn't know Android has a proper built-in qr reader (camera app UX isn't very good for qr), same here. Just learning that and finally uninstalling 3rd party was probably the most important feature of this update...

Don't think I see much in terms of new content here so to add an anecdote about a deprecation post-dating the OP:

My wife and I created an app using the GCP Maps Platform for Unity (or some name similar to it, it was definitely a GCP project) 2-3 years ago. It was for an exhibition, not a long term project though there were aspirations to maybe do something like that. But exhibition ended, and a year or so later the API was sunsetted.

Fast forward to just last week, phones have changed since then, and she wanted to rebuild the app to demo it. I had to say nope, API's gone... But we're lucky to have not actually gone forward with trying to build a business on this despite there definitely must have been people that did and had to migrate to self hosting by force.

Still I use GCP, the UX compared to AWS is just much better, both the APIs (i.e. Terraform) and console (no region!!!). I do know the typical Googler personality and suspect server features like Cloud Run are safe while anything too close to application like analytics is at risk and I'll generally avoid it. I do wonder where auth falls on this spectrum, I'd like to avoid auth0 etc since just too expensive, but it is a bit hard to trust after seeing a shutdown of an app feature.