Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bonesss
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
78 ms
·
841.
▲
by
bonesss
9y ago
Personally I map caps to control because it makes all my text navigation easier (ctrl + a, ctrl + e, ctrl + shift + enter, etc). Plus side: less RSI-feelings in my left wrist. Down side: muscle memory makes you look incompetent on other ma
842.
▲
by
bonesss
9y ago
With Azure they can bill you for the licenses and the computing platform, while also ensuring a pretty impressive degree of lock-in once the platform is sold. Not only are their incentives still out of alignment, the massive consultant ec
843.
▲
by
bonesss
9y ago
Licensing their dev toools gives discounts on tools for development which pushes orgs to buy for-realsies licenses. Partnering with them gives rebates on their dev tools licenses and gives you kickback when you push your customers to buy fo
844.
▲
by
bonesss
9y ago
Click-Once is like... the smartest idea that ever got built by people who have never worked in places that need something like Click-Once. I am of the opinion that if they had dropped the "use apps over the web" angle and focused
845.
▲
by
bonesss
9y ago
What I find missing, compared to back-in-the-day, is the _maturity_ of that ecosystem. Win32 has warts on warts, but around the year 2000 the MS development space was a monoculture and the COM-to-GUI story was increasingly mature and integr
846.
▲
by
bonesss
9y ago
To hazard a guess: a supportive angel investor who wasn't deeply involved in the day-to-day and gave a considered thumbs up to the early plans that were a bit more grounded in concept yet totally untethered from the real-world costs? I
847.
▲
by
bonesss
9y ago
> The citizen, looking the health of their society, has to take a wider view and consider if the existing tax laws and enforcement is contributing to a better or worse society. This is very important in deciding to pay taxes at all, and
848.
▲
by
bonesss
9y ago
Combined with squashing and rebasing git flow leaves a very nice history... I can imagine if you're slamming a bunch of uncurated commit messages along with lots of merges you're gonna see a chaotic history. A consistent history
849.
▲
by
bonesss
9y ago
I'm no proponent of long-lived branches, as such, but isn't holding branches like that in synch that exactly what `git rebase` is for? It's all product specific, naturally, but I've had occasions where isolated multi-mon
850.
▲
by
bonesss
9y ago
I'd go a step further: F# being slightly slow on the uptake of new shiney-shiney-shiney things from MS means you're less likely to hit solutions based on dead product lines and/or tech. A slight moderation in speed to avoid
851.
▲
by
bonesss
9y ago
F# does not need UWP support since MS have allowed ["desktop bridge" apps]( https://github.com/Microsoft/visualfsharp/issues/1096 ) (which may or may not signal the unofficial death of UWP...). The .
852.
▲
by
bonesss
9y ago
I believe that full dotnet core 2.0 support will be something of a watershed moment for F#... .Net on linux has a lot to say for hybrid cloud installations and cloud based development in .Net land. F# is a near-perfect match for many of th
853.
▲
by
bonesss
9y ago
And more specifically: F# is a first-class .Net langauge. That means it has full access to the Base Class Library and cross language interop. It's as "general purpose" as C#, but wildly better for most "general" de
854.
▲
by
bonesss
9y ago
I'd say it's a touch more insidious than that... Microsoft, Oracle, etc: they are highly motivated to present "demo-ware" solutions to half-interested devs to sell their languages (and related high-margin database licens
855.
▲
by
bonesss
9y ago
And, at the end of the day, you gotta assume it's easier to rig-together a "serverless" solution on top of Kubernetes than it will be to make AWS Lambda driven apps into an orchestration solution...
856.
▲
by
bonesss
9y ago
> To my understanding, neither US nor EU law give a crap about the data's geography ... [search warrants... are carried out] based on the citizenship of the targets. Executing a legal search warrant involves using legally binding po
857.
▲
by
bonesss
9y ago
From the article, and I'm no expert: they referred to that other court as a "sister court". My take on that was that those courts reside on the same legal 'tier' so neither one really dictates for the other, SCOTUS
858.
▲
by
bonesss
9y ago
Two things can be true simultaneously... Google, good or evil, has a massive long-running interest in not allowing nations to subvert each others laws. Taken cynically: protecting user data may be entirely incidental to securing megabillion
859.
▲
by
bonesss
9y ago
Point of order: the accusation is not that Google duplicated and replicated data, some of which is outside the country. Google is being accused of intentionally obfuscating their control of the data explicitly to avoid court-orders (and no
860.
▲
by
bonesss
9y ago
> Reality allows more complicated trade-offs than we'll let no-one look at any data/we'll let everyone look at as much data as they want. We're talking about legal precedent for a country to force a multinational to c
861.
▲
by
bonesss
9y ago
> To my understanding, neither US nor EU law give a crap about the data's geography How do you think search warrants and national espionage programs are carried out? ... That's where the law comes in: data is just "propert
862.
▲
by
bonesss
9y ago
> In any realistic architecture, there are are a million exceptions to "this Irish user's data is stored in Ireland": offsite backups, cross-datacenter requests within backend systems, offline analytical stores, queries, d
863.
▲
by
bonesss
9y ago
I'm not selling anything, and you clearly are missing the forest for the trees while making assumptions & assertions about unfamiliar things. CQRS boils down to a single principle: two one-way roads make for easier road maintenance
864.
▲
by
bonesss
9y ago
Commands are objects that express a command. A query is something that provides a value. You can code it up in minutes, and most of the code is pure plumbing to connect to datasources. If that sounds complicated to buy independent control
865.
▲
by
bonesss
9y ago
> The author himself did a retrospective that covers a few issues: https://abdullin.com/lokad-cqrs-retrospective/ Having read the article: veeeeeery little of what is mentioned is related in any meaningful sense to
866.
▲
by
bonesss
9y ago
The entire point of the Separation in CQRS is to avoid unnecessary coupling between reporting concerns, GUI concerns, and user concerns. The act of starting an order does not look like an order. Asking for an order cancellation does not lo
867.
▲
by
bonesss
9y ago
> Some of those are "no, we won't ever implement it" features that will do nothing but eat your data by design. Why would you ever want them in a persistence layer? Cache on memory somewhere better. I feel a significant mo
868.
▲
by
bonesss
9y ago
Ummm sure about that? Something as simple as adding a new required field and maintaining compatability is the explicit use case for Avro. I personally do this in production... I know LinkedIn does too... Seriously: that would be a show st
869.
▲
by
bonesss
9y ago
Through its various protocols Kafka topics can be configured to be guaranteed forwards, backwards, or bi-directionally compatible. That is to say: as flexible as XML or an RDBMS schema with long-term, format encoded, data that can explicitl
870.
▲
by
bonesss
9y ago
Renters insurance continues the payments on the property, maintaining their legal claims in the event of disasters, which was the suggestion I was responding to: that renters not have to pay _anything_ in situations like this. Floods and ot
More ›