I get the impression the "random dude" is the expert you are already paying $100k/yr for. It sends them a slack message, email, etc. The sales pitch is you don't have to code that microservice so you can ship your AI a bit faster. Which is fair enough, since most SaaS is 99% other PaaS/SaaS + some core unique business factor thrown on top. However I worry about how much this company is charging. It is pricey.
The problem is you are saying "API" call so you are already dealing with devs. They can save $10k by writing their own Slack integration (even easier if they pay IFTTT $150/y), and the enterprises will want you to be all FedRAMP, ISO, SOC, Data Resident etc.
I think these are fair comparisons to make. I think the value is less in the slack api integration - anyone can plug in a slack client in afternoon.
When you get to timeouts, escalations, and routing 100+ conversations between 4+ users across multiple slack instances, that's when things got hectic for us.
Make that 6 iterations of such a site, one using wordpress, one using HTML and VIM and no tools, one using an SSG, one using k8s on 4 solar-powered rpis, one using a home-made CMS, and one written in Rust from scratch. Each one with a blog post "Why I...".
Most CSS color names were inherited from the X11 color list [1], which, in turn, sourced its colors from a weird mixture of Crayola crayons, paint samples, and idiosyncratic personal choices [2]. It's a mess.
Not who you are replying to, but I started learning HTML/CSS right when HTML5 and CSS3 had just come out, so I do have somewhat of a soft spot for these
Yes, I've always thought they were excellent logos. Makes me nostalgic about the optimism of this time.
Also people actually use them, a while back every CS student inexplicably had these stickers on their laptop. I can't see these new logos being ever used as stickers because they're just... nothing.
As someone coming back to frontend after ten years... the optimism was justified! Writing UI code is amazing now.
Don't let the warts of the real implementation get you down, it's a delight how everything I want to do is just part of the vanilla stack now, one way or another.
I'm not even convinced that html and css need logos. Those shield logos always made me think they were trying to sell you something, which is weird for a markup language.
What is color blind unfriendly about the new logos precisely? Which variant of color blindness will not be able to read them?
Which visual impairment exactly will find it easier to parse the previous logos (which are a mess of design scarcely related to the actual technology name) than the current ones, which contain thick bold text indicating exactly what the technology is called?
> Do not rely on color alone to denote information
> Use additional cues or information to convey content
The old icons were certainly ugly. But they had a unique shape (cue) and didn't rely on color. The new logo has text which helps, but this is where visual impairment becomes an issue (lack of focus to read said text).
I have no intent to take away from the meaningful choices made in this logo's design. But even just picking a unique shape for each component would go a long way.
The old CSS and HTML logos had identical shape aside from the text. The new CSS and HTML logos have different shape (albeit subtle), larger text, and a greater difference in lightness.
In this shovel rush, even the shovel factory makers (OpenAI) are not sustainable, and the shovel factory factory makers (NVidia) are doing well. Ironically the "gold" is with all the boring companies on the consumer side of the AI.
You avoid a seed phrase, but how? I thought it was "not your keys not your coin".
My understanding is someone who wants secure crypto needs to cryptographically safely generate a seed phrase. For signigicant amounts of money you will want that backed up. I guess if this is like a $50 gift card people are treating it like that and might accept if it gets lost then shrug.
Burner comes with a pre-generated key or you can request that it generate a new key with entropy you supply (in part, it's hashed with entropy from multiple sources). In both cases you always need to trust the hardware, but this is true with any hardware wallet.
I would always recommend using a multisig for storing large amounts of funds regardless of the wallet vendor.
