Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dagss
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
50 ms
·
481.
▲
by
dagss
8y ago
What documentation though? Cosmos' documentation is appalling... it is not like you can learn these things from it. With Cosmos you are always on your own, trial and error, to figure out how it behaves
482.
▲
Is USA Old-Fashioned? (Norwegian)
(translate.googleusercontent.com)
1 points
by
dagss
8y ago
|
0 comments
483.
▲
by
dagss
8y ago
Think about two dark matter clouds crashing into each other. Each cloud just continues with the same speed in the direction it had. They dont interact other than gtavitationally. After passing each other they start to pull on each other gra
484.
▲
by
dagss
8y ago
No experience with D, but using Go a lot, and it is the same thing there with lack of metaprogramming. Turns out everyone uses reflection instead to get anything done. Not sure how much of a success that is.
485.
▲
by
dagss
8y ago
First off, for small tables, you always take the hash value modulo some small number like 10000. Who cares how good the hash function is, if you end up with 1/10000 chance of collision in the end anyway? Speed is obviously more importa
486.
▲
by
dagss
8y ago
Actually I wonder if your reasoning is circular.. If you saw a coupled mess of microservices with a lot of technical debt you would probably say that it is not "Microservices" because it is violating the Single Responsibility Prin
487.
▲
by
dagss
8y ago
I am not convinced that microservices always causes less coupling as you claim. Sometimes the coupling just jumps into the network/API layer. (Why would it not?) This can happen unless your initial divison into services was perfect (an
488.
▲
by
dagss
8y ago
He is explaining it further down! For instance, he cannot set a breakpoint and follow execution flow (because suddenly the flow resumes in another microservice) It seems from your comment that you assume one can always work with only one se
489.
▲
by
dagss
8y ago
You have an assumption that the initial design/division of responsibility into microservices was perfect. If not, then no, the unintended coupling is not limited to within a service, it will find its way to the API between the services
490.
▲
by
dagss
8y ago
But behold the coupled mess you get if your up front design (the boundaries between the microservices) wasn't perfectly chosen or isn't robust against spec changes. Can easily happen for instance when architects that are too remov
491.
▲
by
dagss
8y ago
Well in that context, red meat is obviously healthier if you know up front that the people in question are going to pile on dressing ... Context is everything. I am mainly advocating that it depends on the kind of coders on the teams, how
492.
▲
by
dagss
8y ago
Well, but some services composed of microservices turn into a distributed spaghetti monolith though. They only "naturally decouple" if you draw the lines between units correctly in the first place. And if you are able to do that w
493.
▲
by
dagss
8y ago
IMO if you are writing backend code where it is difficult to insert fakes at any point where you need to test, then all bets are off anyway. Doesn't matter if you use monoliths or microservices. If you can't abstract out some depe
494.
▲
by
dagss
8y ago
It is possible to build balls of mud either with microservices or larger-sized services. There are pros and cons to both. But when "easier testing" (from OP) is said to be an advantage of microservices specifically...I am not sure
495.
▲
by
dagss
8y ago
What you say you want is XSLT though, just wity a better syntax and for YAML. XSLT was just fine, had a lot of very good ideas, just horrible syntax. Horrible syntax is kind of a forgivable offense, lots of things have horrible syntax and
496.
▲
by
dagss
8y ago
I definitely want those things you say done on the feature branch. Whether push to production happens before or after integration to master isn't critical, but it should be a close 1:1 between master and prod (within minutes).
497.
▲
by
dagss
8y ago
A nice thing about merges is: If you have CI on every PR, and you require all merges into master to be fast-forward merges, then you a) guarantee that master is always green and b) don't need to run CI again on the master branch. If yo
498.
▲
by
dagss
8y ago
I need tiling window managers. Not negotiable at all. I have the impression that there are no alternatives for Windows or Mac? If so that alone frees med from considering those..
499.
▲
by
dagss
8y ago
Same in Norway, but most people like to save those costs. Delivery is rather expensive. Perhaps higher minimum wage drives tow bar adoption...
500.
▲
by
dagss
8y ago
There are plenty of studies on this from my quick Google searches, some better than others. Disregard the one funded by oil industry that assume without further comments that batteries are discarded after 150 000 km, that is not a good assu
501.
▲
by
dagss
8y ago
Cannot legally add a tow hitch in Norway though.
502.
▲
by
dagss
8y ago
Roof rack: Skis. (And the Model X ski box behind car on tow bar solution look unwieldy and ridiculous, but there are still lots of them around here, as the only EV compromise that sort of ticks all the boxes.) And kayaks too. Tow bar: Not s
503.
▲
by
dagss
8y ago
Illegal in Norway though. I just got a Model S actually, and am considering installing a hitch for carrying bikes. But I would NEVER pull a trailer.. What if I do, and my trailer collides with something/someone, and I become liable for
504.
▲
by
dagss
8y ago
On the other hand, the number of cars per Norwegian has increased by 18% since 2005, and the trend is continued growth in cars per capita. So the EVs are not displacing fossil fuel cars, they come in addition. (Probably there would have bee
505.
▲
by
dagss
8y ago
And this is despite all the options of electric cars on the market failing to live up to the average Norwegian's criteria. Many Norwegians are still waiting for a "real" electric car to become available. Where a real car is d
506.
▲
by
dagss
8y ago
Our git repo for a backend service contains dozens of packages, and many small packages is recommended in go, and they do need to import one another... I guess it is not all that different from Python, with Python you need to add the source
507.
▲
by
dagss
8y ago
GOPATH behaves very, very differently from PYTHON_PATH and CLASSPATH, it is not the same thing at all. Basically before go 1.11, it was impossible to just do git clone ... somedir cd somedir # build code and run something Y
508.
▲
by
dagss
8y ago
When people consider float vs int, performance is seldom a relevant factor. You have to ask, what do you even mean if you use floating point for representing money? If you use floating point, the whole point is that you want the behaviour
509.
▲
by
dagss
8y ago
Yes the usecase was for a readonly connection.
510.
▲
by
dagss
8y ago
An alternative to doing file based SFTP is to just treat SFTP like an API. A company I work for implemented an SFTP service where every operation simply translates to some SQL DB lookup. And a file download kicks off a larger SQL query and
More ›