fwiw I just threw this in since many on HN probably don’t know much about Reading
red face
933 karma · joined July 15, 2023
fwiw I just threw this in since many on HN probably don’t know much about Reading
red face
that’s ~ 45 ft underground, I believe … perhaps not that impressive, but quite funny since I would hesitate to undermine my own house and surely this makes it worth less
guilty as charged (but also with experience that I have made something cool that I would not otherwise have had the skills or time to do)
> same fashion as a group project in school
you describe my approach to schoolwork with uncanny accuracy
> that’s the funnest part!
amazingly, finding a name for a new PL is the hardest part and yes I plead guilty to working collaboratively with an LLM for inspiration and for grunt checks (motorbike for the mind)
Until then, I subscribe to the view that strong types fit LLM coding well since LLMs are prone to make silly mistakes when they patch together code examples in dynamic languages.
[Disclosure, my new language https://bil-lang.org aims to add “strong typing” around parallel programming to help weed out deadlock conditions.]
It inspired me to create a similar post for the Bil concurrency model: https://bil-lang.org/bil-concurrency-distilled/
don’t get too excited until we get the TinyGo backend built though ;-)
Show me a well designed md centric notes taker that uses my own drive, syncs between Apple devices, has no subscription and I am listening.
So I scrolled (and scrolled) through your website to find the pricing section, and finally unearthed your very cryptic note about paying for the power option that allows me to sync. This raises three red flags to me:
1. it is hidden and is similar to typical trick clauses that many software products vendors play … you reserve the right to hold back a key feature and make it payable
2. it is cryptic - as you say your product is free on my devices and on web and it is shareable … maybe I can use dropbox to sync, but maybe not … now I have to invest effort to test the limits
3. nothing prevents you from drawing the line quite high for now, but then playing more and more stuff behind your paywall over time, forgive me but (1) has already lowered my trust in you
Now - thank you for offering me a free subscription for one year … but I don’t want to strand a years’ worth of my notes behind a proprietary paywall. This tells me that (i) your intent is to take my money and (ii) you don’t understand my objection. So no thanks for the free puppy.So here now, I am out. To get me in, you need to win back my trust. Not easy. But your product is very cool. So I make you a counter offer:
1. make your product free for ever including synching across the Apple ecosystem to all personal users
2. look at a product like BBEdit and adopt their freemium model where business users must pay a fair fee and it is enforced via a self declaration or maybe where folk want to collaborate with 3+ colleagues or something (I want you to make money, but I will not pay a subscription for device synching a text editor)
3. open source your code so I can fork and build myself if you go under a bus
4. make your policy clear and upfront (a pricing section with free vs paid comparison would be good) Is it really free?
Yes. The editor and local files stay free, with no account
required. Beauty Maximus is an optional subscription for
keeping a library current across Apple devices and for meeting
notes that transcribe and summarize on device.
so not free as in open source, nor free as in beer eitherhttps://bil-lang.org aims to address this gap … I wrote a post about Bil’s adjustments to Go here https://bil-lang.org/blog/rethinking-classical-concurrency-p...
one day the backbone (E1 bidirectional ring iirc) was broken north of london … my boss drove out to find that travellers had entered the field, opened the inspection cover in the ground, stood a pole for their clothes line and filled with cement
very savvy, he didn’t let on that we had about £1m revenue per day close to collapse and convinced them to hang their clothes somewhere else (perhaps a few quid changed hands)
the 1064 was the vanilla IEEE P754 64-bit pipeline and the 1067 added Intel bus interface