test comment
blahlqjbwejlkblrq
blahnmeqwflbeqlwblew
blahkasjflkanweklqwbfkelbqlfbklqweblfkbq
Bring Your Own Client
151–160 of 262 posts
Re: Bring Your Own Client
#152blah
Re: Bring Your Own Client
#153> even if Google wanted to expose an API for editing Google Docs in third-party editors, it would probably be very challenging
It does, https://developers.google.com/docs/api/reference/rest/v1/doc...
The reality is that building an editor for text is easy. Building a rich text editor is faaaaaaar from being a simple thing
Re: Bring Your Own Client
#154Small note: Trello has an excellent API - it is my goto example of a pleasant API to work with as an end user.
That means you can "bring your own client", I have a "todo today" list that I pull via the API and display via conky right on my desktop.
Re: Bring Your Own Client
#155The competitive advantages of owning both the application and the data are so high that don't see widespread BYOC ever happening without government intervention. I'd like to see an enforced separation in law between commercial application providers and storage providers. So, if someone writes an app like Google Docs, they can't just store the data opaquely on their own cloud servers. They legally have to integrate wi…
I think it's not completely inconceivable that this could be regulated some day with music streaming. There are zero technical hurdles (unlike with complex apps like Google docs), and because there is such potential for decoupling the client the consumer benefits would likely be much greater. I've been meaning to switch from Apple Music to Spotify for a while now (I'm on Android). I just had a look around the Spotify…
You should check out Spot[0]. It's a Spotify client written in Rust using GTK. It's quite barebones at the moment and only works with premium accounts, but the interface is much cleaner than the official Spotify client.
Re: Bring Your Own Client
#156I’m reading Thinking Forth at the moment and there’s a part in the description of Forth about how it decouples words from their parameters and return types by only allowing stack manipulation. This means that all words share a common interface and so they’re infinitely composable. The reason I started reading this book is due to learning how WebAssembly works which turns out to be quite similar to Forth. It got me th…
Yup yup. I'm on the trail of just this using a purely functional Forth-like language called Joy.
Your hunch is correct, you're intuiting the "Categorical" (as in Category Theory) nature of "point-free" format:
http://conal.net/papers/compiling-to-categories/
> It is well-known that the simply typed lambda-calculus is modeled by any cartesian closed category (CCC). This correspondence suggests giving typed functional programs a variety of interpretations, each corresponding to a different category. ... This paper describes such an implementation and demonstrates its use for a variety of interpretations including hardware circuits, automatic differentiation, incremental computation, and interval analysis. ... The general technique appears to provide a compelling alternative to deeply embedded domain-specific languages.
Re: Bring Your Own Client
#157Small note: Trello has an excellent API - it is my goto example of a pleasant API to work with as an end user. That means you can "bring your own client", I have a "todo today" list that I pull via the API and display via conky right on my desktop.
Part of the problem is that APIs are intrinsically harder to interop with than a local file format, for fundamental reasons like latency and shared state that others might modify from underneath you. You couldn't just read once at the beginning and then keep things in synchronous memory thereafter, persisting as needed but never reading again.
Of course that doesn't mean the accessibility situation couldn't be improved with (for example) more standardized APIs, better documentation/discoverability, etc. iOS Shortcuts make it easy to work with third-party services; what would the equivalent in a real programming context look like? There's probably some interesting brainstorming to be done here.
Re: Bring Your Own Client
#158Earlier quoted context omitted.
Calendaring is a huge embarrassment and a mess, and it is super annoying if you have to deal with anyone “outside” your group. Emailed ical files seems to be the norm but only work over email. :(
Calendaring is surprisingly complex. Especially when it comes to stuff like rules for repeating events and timezones. I had to do work on this at a previous job and it was pretty hard even with all the libraries and tools out there.
It's insanely complex - one of those problems that is easy to state and nearly impossible to solve (which means there's opportunity here).
Re: Bring Your Own Client
#159Earlier quoted context omitted.
For something to get traction, it has to have excellent UI and UX. So far open source hasn't been very successful at providing that since there is no economic model to finance the immense amount of work required for good UX.
I posited a similar point to a former colleague (mine was more about eventual market dominance due to excellent UI+UX), and he came back with Craigslist as a perfect example of a product that gained a massive user base well into an era where its UI felt very outdated. A few years after this exchange, I feel more like I was right about my point: FB Marketplace has almost completely taken over as far as a classified pr…
Another counter example: amazon. By far the worst userinterface of any webbshop, no filters, hardly any categories a search were very small changes in spelling/wording make huge changes in results. And still they are by far the biggest game in town.
Re: Bring Your Own Client
#160I'm in medicine, and I desperately want this model for electronic health records. The current state of lock-in has been effectively maintained by the entrenched players, and it's really bad.
Since HLX has become increasingly required, I've seen that the lock-in doesn't mean diddly squat. Now we're not "locked in", but for my new vendor to drop-in means I have to pay an extra "API Fee" for them to whip up the API interface to pull everything from the old EMR and into the new EMR. So either we get to the point where we are legislating perfect compatibility (and I can't imagine how good EMRs will get once t…
I saw that you doubled down on [this comment](https://news.ycombinator.com/item?id=26181228). Week 5 excess mortality for 65+ in Israel is now up to 7.4 times above normal. It increased every update for the last three weeks. Unbelievable that people like you take 1 minute to read something, think you are an expert and try and proclaim victory. I'm 100% sure you will double down again instead of taking the honorable path of admitting you were wrong. People like you never get held accountable.