Coupled with a red square that follows the mouse pointer is the one-two knockout of annoying mouse UX.
1,281 karma · joined March 19, 2013
Happy to chat. Ping me on marty [at] orbitalhq dot com
It's not super serious, but it's not meant to be -- it's not pitching to be your enterprise AI strategy. However, even though it's presented in a playful way, I suspect it's quite powerful, and expect The Internets will build some cool stuff atop it.
It's a fun and creative way to explore playing with LLM's, and it's brilliantly executed! Happy to see it here on HN.
This is a sample of 1 usecase, (so questionable real-worldness) but the difference is really eye-opening. Congrats to the C# team!
Thanks for sharing.
That's an INSANE amount of time which - as you say - could be spent learning to play the piano solo from Scenes from an Italian Restaurant.
Angular code wouldn't use any of these techniques:
- the use of Proxy()
- calling compile(),
- using a querySelector to bind elements
- Manually wiring up click handlers
In that context, it's probably relevant to show this (assuming it's indicative of what Angular actually does -- of that I'm less sure)
Given that, it's a bold choice to include Lombok in a library that other developers will pull into their stack - it's likely to make this a non-starter from those in the 'no' camp.
As Lombok is just compiler sugar, when building an SDK for other developers, it's probably less alienating to just write the boilerplate that Lombok saves you from.
Theming has moved on a fair bit too...
I recently did a quick re-check of the landscape, and for our purposes, Propel still is the only provider that works. I was surprised to find that support for Machine-to-Machine API auth (ie., standard OAuth) isn't well supported.
Likewise, OIDC support is patchy amongst the other providers. I reached out to Clerk support, and for both these use cases, they weren't supported.
Propel is great.
Some minor feedback - I went to the website to look for pricing (scanned the header bar), and couldn't find it.
Didn't think to look in the docs, as it's almost always available from the homepage.
Appreciate you linking it here,but if I hadn't come from HN, I'd assume this is a "contact us for pricing" situation, which is a bit of a turnoff.
Developer plants an easter egg. It was a good one ... and it was a reasonable assumption it wasn't gonna break anything. Several people have a good chuckle. Someone gets affected negatively by it, so the developer says, "fair play, that wasn't the intent, let's remove it". Everyone hugs it out and moves on.
I have no idea if this was the full story, or if his Twitter was aflame with negativity, but I imagine if this happened today, the tone would be much more combative than the exchange on the Stack Overflow page (eg: this HN thread, which is full of 'Easter Eggs Bad! Bugs!') -- which is a real shame.
If humour be the bugs of life, play on.
That's disappointing. I wonder if it's related to legal issues, technical issues, or just doing a phased rollout?
https://www.elastic.co/blog/elasticsearch-is-open-source-aga...
I've been a Kotlin dude for a very long time, and am a bit out-of-date on other languages.
What are languages that handle this nicely, without needing libraries?
Starter - Free Pro - $24 / Editor / Month
https://www.lottielab.com/pricing
(Not affiliated)
If you go to the website, there's nothing on their front-page. The post on their blog (https://www.crowdstrike.com/blog/statement-on-windows-sensor...) doesn't even link to the solution. There's no link to "Support Portal" anywhere to be seen on their front-page. So, you have to go digging to find the update.
And the "Fix" that they've "Deployed" requires someone to go to Every. Single. Machine. Companies with fleets of 50k machines are on this HN thread - how are they supposed to visit every machine?!?!
> Simon Shindler contributed significantly to the aesthetic of Figure 7, but could not be named an author for obvious reasons.
$1M ARR with an 8 person team is by no means "doing great". Assuming 20% of income goes to overheads (such as hosting, marketing, legal, accounting), that leaves a salary of $100k for each staff member. Even if they had 0 overhead, this is still only $125k each -- that's hardly big money.
Also, in reading the post - I find little to object to. They're not changing their license. They're not doing anything to prevent self-hosting.
They're making it clear they're not offering support to people who don't pay (completely reasonable), and gatekeeping a few features that add value - while still giving away a huge amount for free. That's a fair deal to ensure the company remains viable, which is in everyone's best interest. In practice, this decision is unlikely to materially impact anyone.
Open source is a gift, not a right, and certainly not an obligation - and from what I can see, they're not doing anything here that undermines the Open Source-ness of their offering.
FWIW, I'm not sure you'd find an alternative analytics offering that's both commercially viable, and "more open" than what Plausible are offering today.
It's also been ported to Angular:
This isn't easily discoverable from the landing page -- I think the site could benefit from an "examples" sections. Given the focus on customizability, it'd be good to get a sense of what's possible, rather than diving straight into Get Started, before I've decided that I want to use the tool.
You've only presented half the story. They're also Open Source (Apache 2.0), with code on github.
As you mention, some features are gated, but they seem to have a fairly solid OSS offering.
we have the same strategy for testing against Kafka., etc.
where we care about data, we seed the db with data for a specific group of tests. Otherwise, we just nuke the db between each test.
Prior to doing this, we'd use in-memory db for tests, and a real db for runtime, using JPA / Hibernate to make things transferrable. But this was leaky, and some things would pass in tests then fail at runtime (or vice versa)
TestContainers has been so much better, as we're running against a real version of the database, so much smaller chance of test and runtime diverging.