If people actually like it we should take a performance pass. In our defense, we at least switched out the original bmp files from the first pass we took at hacking this together.
4,503 karma · joined January 21, 2013
[ my public key: https://keybase.io/mmcc; my proof: https://keybase.io/mmcc/sigs/2TecG4FqAN88M5UaETYwdA4JegapEYa3ojaIrONVVDo ]
If people actually like it we should take a performance pass. In our defense, we at least switched out the original bmp files from the first pass we took at hacking this together.
[1] https://www.mux.com/blog/your-browser-and-my-browser-see-dif...
I suspect the answer is "no" here, but can Stack be used as an OAuth provider itself? I think all I see in the documentation is using other OAuth providers for authentication.
I always liked this idea, and I a few cryptocurrencies/blockchains tried to do something like it, including Stellar Lumens[1]. Just looked it up to post this and they abandoned it back in 2019.
Unlike the tokens of other blockchains, lumens aren’t mined or awarded by the protocol over time. Instead, 100 billion lumens were created when the Stellar network went live, and for the first 5 or so years of Stellar’s existence, the supply of lumens also increased by 1% annually, by design.
That inflation mechanism was ended by community vote in October 2019. And in November 2019, the overall lumen supply was reduced. Now there are about 50 billion lumens, total, in existence, and no more lumens will be created.
[1] https://stellar.org/learn/lumensEither way, looked it up out of curiosity: Audi's parent company, Volkswagen, currently has a market cap of ~58B EUR with revenue over 300B EUR in 2023. Tesla has a market cap of $772B with revenue just under $100B in 2023.
Tesla's stock is trading (and has) at a staggering multiple for the automotive industry. It's fair to call out that their competitors may have their own struggles, but negative growth in Tesla's primary product line is going to make it increasingly tough for investors to stomach that premium.
Elon has a gift for selling a vision, so I certainly wouldn't bet against Tesla on any short-term horizon, but I struggle to imagine that alone will be able to carry their stock price in perpetuity.
Started to make sense when I checked the website and their business model is charging for updated Chrome binaries: https://pro.chromiumforlambda.org/
I use the physical buttons if I’m reading on a plane or otherwise sitting down, but I much prefer holding the kindle from the back if I’m reading lying down. I assumed that must be rare given how little attention any of the e-reader form factors have given to it.
Feels pretty wild/cool to say it might almost be too fast (in terms of feeling natural).
From Alfazeta's page (including the typos). 15 frames per second feels pretty wild, but would also, unfortunately, change this math pretty considerably if you ran it full tilt.
> Cross-platform: NodeSwift works not only on macOS, but also on Linux, Windows, and even iOS!
Now I'm curious about the iOS bit. Is that intended for React Native?
> Although all debts will be paid in full, plus interest, nothing will be leftover for equity holders
> Depending on the type of claim they hold in the case, some creditors could recover as much as 142% of what they are owed. The vast majority of customers, however, will likely get 118% of what they had on the FTX platform the day the company entered Chapter 11 bankruptcy.
Lately I've had a solid experience using Replicate for specific models depending on what I want to do.
[1]: https://thehive.ai
In the end...ongoing maintenance there was still enough of a pain that we made the decision to outsource it. For just one or two SDKs I think we probably would have kept going with it, though.
[1] https://github.com/OpenAPITools/openapi-generator
[2] https://www.mux.com/blog/an-adventure-in-openapi-v3-api-code...
The biggest reason we started working with Stainless was to migrate from the open source generator process we were struggling with, but actually ended up transitioning our hand-rolled Node/JS SDK first because it's both our most popular SDK and because the fragmentation of the JS ecosystem has been a surprisingly big headache[1]. Went into it for reduced maintenance, came out pleasantly surprised at how useful I was finding my own SDK's features around `for...of` on paginated routes, etc.
Congrats on the launch, Stainless crew!
[1] https://www.mux.com/blog/keeping-up-with-the-node-ish-ecosys...
This post has 226 points, 234 comments, posted ~2 hours ago, and went from the front page to >#100 between two refreshes.
The most popular layoff post had 143 points, 220 comments, posted 5 hours ago and I can't even find it outside of search: https://news.ycombinator.com/item?id=40038549
I didn't see anything in the docs, but I would love for someone to tell me this exists.
Re: the post itself, this was much more compelling than TypeSpec's website imo. At the very least it feels like some of these examples, such as the enum bit, should be ported there. Also interesting that there isn't a single mention of languages like Cue[1].
both OpenAI and Google rely on scraping as their foundation for…everything.
OpenAI and Google also (claim to) respect the most basic bot deterrent, robots.txt, with their crawlers. If someone doesn't want their content scraped to be included by search indexes or LLMs/models, then that certainly includes "smaller indie hackers."> Our data includes anonymized API calls to traditional search indexes like Google, Yandex, Mojeek and Brave, specialized search engines like Marginalia, and sources of vertical information like Apple, Wikipedia, Open Meteo, Yelp, TripAdvisor and other APIs. Typically every search query on Kagi will call a number of different sources at the same time, all with the purpose of bringing the best possible search results to the user.
source: https://help.kagi.com/kagi/search-details/search-sources.htm...
On the other hand, there are a lot of people right now that want to keep stuff accessible to humans and not have it scraped for models. I know the lid's completely off the box on that front so it's probably useless to fight it, but seeing products explicitly designed to circumvent bot prevention feels kinda bad.
The thing I find the most valuable about Copilot is it living directly in VSCode. Understand it's not trivial and this has one public commit, but long-term do you have plans to move closer to the editor?
How do you see this in relation to other projects like continue.dev?