remon

13 ms·

91.
by remon 12y ago
This seems to be similar in scope and architecture as Microsoft's Orleans. Interesting. EDIT : After more careful review noticed this : "It was developed by BioWare, a division of Electronic Arts, and is heavily inspired by the Or
92.
by remon 12y ago
I made a little bet with myself when I saw the topic of this post that a good 80% or more of the top comments would be of the "Shouldn't jump on the MongoDB/NoSQL bandwagon, nothing wrong with SQL" variety combined with
93.
by remon 12y ago
My personal favorite : "That's the earth of the beast". In dutch it's "Aard van het beestje" which loosely translates to "it's in its/their nature". During a large conference in Cannes, Fran
94.
by remon 12y ago
Hardware fails. This architecture has single points of failures which means if one of those instances fails the entire system goes down. This is generally not acceptable for environments with 1 million active users (which implies high busin
95.
by remon 12y ago
I suppose there is some value to this as a thought experiment but pretty much every tier in that architecture has breaking flaws. The most relevant being that anything that has an audience of 1 million users cannot run on an architecture th
96.
by remon 12y ago
I understand what you're saying and you make good points but I still do not think removing a loop as a language feature is necessarily an interesting goal. Generally speaking this discussion tends to revolve around reducing verbosity o
97.
by remon 12y ago
This was exactly what I was thinking when I read the code. The goal should not be to remove loops. As a language construct there is nothing wrong with loops itself. The goal should be to make more readable and maintainable code, preferably
98.
by remon 12y ago
Ah thank you. Fun read.
99.
by remon 12y ago
That seems the correct one : https://cs.nyu.edu/~yap/classes/os/resources/origin_of_PV.ht...
100.
by remon 12y ago
I'm not very comfortable with storage engines that directly build on memory mapped files. MongoDB's current storage engine is mmap based and it's sub optimal at best which is undoubtedly part of the reason they're buildi
101.
Global Websites Hacked by Syrian Electronic Army(cnbc.com)
6 points by remon 12y ago|0 comments
102.
by remon 12y ago
Fascinating read. It never fails to amaze me how far compilers have come over the past two decades.
103.
by remon 12y ago
I didn't argue JavaScript is #1 on the server side, simply that it's the language with the most traction when it comes to that group of languages (of which Python is no part by the way, PHP and Ruby are though). I wouldn't to
104.
by remon 12y ago
I think in this instance JavaScript has to compete with Java, C#, go, erlang, etc. rather than the other "scripting" languages. I don't think many would argue JavaScript isn't comfortably #1 within that domain.
105.
by remon 12y ago
I think you've touched upon the strongest argument for using JavaScript within a server stack. That said, that argument seems less strong for companies the size of Netflix, Yahoo, and so on. They don't exactly have problems recrui
106.
by remon 12y ago
Fair point. I suppose the debate should be about API and "lower" tiers mostly.
107.
by remon 12y ago
I would argue the discussion is less about which framework and more about the suitability of the language. It's a debate worth having but I struggle to think of good arguments to move infrastructure of this sort of scope to JavaScript
108.
by remon 12y ago
What an odd trend. First Netflix moves part of their infrastructure to Node ( https://news.ycombinator.com/item?id=8631022 ) and now Yahoo is doing something similar. Node.js is great but I don't think huge enterprise sy
109.
by remon 12y ago
This is one of three HN links on the front page that uses this new fad where the landing consists of nothing but a full screen image, no content and a less than obvious notification that you should scroll down to see something actually usef
110.
by remon 12y ago
Why do you consider joins a big differentiating feature for NoSQL storage solutions?
111.
by remon 12y ago
That may be generally true but those two things are not mutually exclusive. Scalability doesn't come at the expense of getting things right, it just might come at the expense of certain features which applies to most distributed system
112.
by remon 12y ago
That almost certainly implies you're not working on anything that requires horizontal scalability. That's a luxury not everyone can afford. Scalability, in almost all cases that actually require it, is the first priority. It'
113.
by remon 12y ago
Why on earth would it be too late? MongoDB is comfortably in the top 3 in terms of traction and they just fixed what many consider the primary technical argument against using it. Too late for what?
114.
by remon 12y ago
I agree. I was referring to the actual cost of the cycles but there are many situation where you need to find a balance between cost and fluent user experiences. My point was primarily that the consideration that server side resources are m
115.
by remon 12y ago
It's not so much a scalability issue as a cost-per-user issue. Obviously client rendering performance (or lack thereof) is a concern and if server side rendering solves that for a manageable increase in cost that's perfectly fin
116.
by remon 12y ago
I'm glad I wasn't the only one that needed a few seconds to understand what was going on. I didn't bother reading it.
117.
by remon 12y ago
Yes, yes it is. For a number of reasons but the most overlooked one is that server CPU cycles and client CPU are not equally expensive.
118.
by remon 12y ago
Server side rendering has significant upsides but I feel one of the biggest downsides is consistently ignored when discussing it, namely that when you render (parts of) pages you burn expensive server side CPU cycles rather than the free cl
119.
by remon 12y ago
This full-page-jumbotron-without-any-indication-you-should-scroll-down thing (is there a proper name for that) has to stop.
120.
by remon 12y ago
The problem with arguments like these is that there being "no good reason" is highly subjective. Excessive change is generally better than no changes at all. Things have to evolve and even if we miss the mark every now and then it

More ›