Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
javascriptlol
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
91.
▲
by
javascriptlol
15y ago
Unfortunately, there will be no UDP protocols. So we're not quite back to where we were in 1970 yet.
92.
▲
by
javascriptlol
15y ago
You presuppose several things: 1) that "analytical" thinking (whatever that even means) is superior to "emotional" thinking, and 2) that benefits can be boiled down to economic nonsense (e.g. "money", "happiness").
93.
▲
by
javascriptlol
15y ago
I dispute the existence of "resources" in the abstract sense people are trying to achieve with respect to REST. The web is just a collection of stuff with ephemeral links to go from thing to thing. Obviously, these could be called "resource
94.
▲
by
javascriptlol
15y ago
The fact that you think it us "usually" a valid assumption is exactly the conceit I am talking about. It's only "usually" assumed to be true because the people who have different requirements don't come to the web because it's such a limp p
95.
▲
by
javascriptlol
15y ago
I never said my experience was universal, nor did I imply it. So what's your point?
96.
▲
by
javascriptlol
15y ago
Unfortunately, during our circle back to the 1970's we lost UDP, which is essential for real time protocols.
97.
▲
by
javascriptlol
15y ago
The web was never a set of "addressable, reusable resources".
98.
▲
by
javascriptlol
15y ago
And btw, the point I am making is not against high level constructs. Once you have sockets you can build whatever you like. The problem is HTTP is the bottom level of the web. If you had proper facilities at the bottom you could have your H
99.
▲
by
javascriptlol
15y ago
>You don't, of course, but it's usually a pretty reasonable assumption that the effort involved in implementing your own (reliable stream sockets|scheduler and memory manager|high level language compiler) will eclipse severalfold any ad
100.
▲
by
javascriptlol
15y ago
Again, downvotes but no comments. How embarrassing for HN that the crowd here can't justify their position.
101.
▲
by
javascriptlol
15y ago
Who actually uses or needs this kind of tooling? What exatly is "multi-service coordination" and why should anyone non-academic building actual systems care what it means? HATEOAS doesn't solve the problem anyway. What happens when a field
102.
▲
by
javascriptlol
15y ago
Still waiting for your answer.
103.
▲
by
javascriptlol
15y ago
Please downvote this comment too. The more you downvote me without commenting, the more you confirm my superior skills in system design.
104.
▲
by
javascriptlol
15y ago
Can't see why you're being downvoted here. I think it's a reptilian defensive response from the REST academics.
105.
▲
by
javascriptlol
15y ago
Wow, what a weak crowd. No substantive criticism, just downvotes. The HN crowd should please refrain from arguing on the Internet about design until they've learned some basic systems programming.
106.
▲
by
javascriptlol
15y ago
What? How can you say REST is going to give you a bunch of stuff "for free" when you haven't even seen the application. How do you know you're even going to get what you want? This is the central conceit here.
107.
▲
by
javascriptlol
15y ago
Don't downvote, comment. Or admit to yourself that you can't respond to my criticism.
108.
▲
by
javascriptlol
15y ago
If I want to raise my blood pressure into the 180's all I have to do is open a thread about web design "principles". He has the perfect anti-example for HATEOAS right in there: financial transactions. You would never in 1 million years want
109.
▲
by
javascriptlol
15y ago
The problem is designing all this nonsense into the bottom layer in the first place. I've never heard a good argument as to why any of this is better than just starting with raw sockets for an app talking to a server. Take HATEOAS for examp
110.
▲
by
javascriptlol
15y ago
I'm not saying the govt should regulate Zynga. I'm pointing out that they do regulate slot machines. That's because people know slot machines can be bad for people, and are generally a pointless waste of time and money that feel good in the
111.
▲
by
javascriptlol
15y ago
>We're still in the infancy here in learning how to harness mobile devices to make better products. What this unpacks to: Let's make some money before people realise what's up.
112.
▲
by
javascriptlol
15y ago
If pg is sitting off in the background trying to convince people to click buttons with zero thought being exercised, then yes, Hacker News should be voluntarily time-limited. Until then, it is an apples-and-oranges comparison. Video games a
113.
▲
by
javascriptlol
15y ago
So why don't you put a strict limit/spend limit on the game? Because you don't care about the ethics, except insofar as it sticks to you.
114.
▲
by
javascriptlol
15y ago
People have the right to decide whether they smoke cigarettes, too. But most people can see it's a harmful addiction and that it is plain unethical to profit from it. And yeah, I think World of Warcraft falls into the same category. Why don
115.
▲
by
javascriptlol
15y ago
This is the problem with large businesses; they can always say the supposed positives to the majority outweigh the real harms they are doing to a minority. Don't you think inducing people to click on stuff over and over with absolutely no s
116.
▲
by
javascriptlol
15y ago
So, because sometimes you get it wrong you should go through life without considering the consequences of your actions? I don't think that's a good way to approach ethics. A better idea would be to learn from these incidents, speak out agai
117.
▲
by
javascriptlol
15y ago
It's a disturbing feature of modernism that people are hyper-focused on "evidence". Most studies are pretty inconclusive anyway. People know, in their heart of hearts that these games are pointless and exploitative. We don't know what the e
118.
▲
by
javascriptlol
15y ago
It's pretty obvious that these games are just elaborate slot machines. Like slot machines, the companies involved simply don't care about the ethical issues. And you're apparently happy to profit off these activities until the evidence stic
119.
▲
by
javascriptlol
15y ago
>But now that I think about it, I realize why people have a hard time understanding REST. It's not a "design" constraint any more than OOP is. It's an implementation constraint. Your attempt to enforce some dichotomy between design and
120.
▲
by
javascriptlol
15y ago
The first run will be intolerably slow. Caching will not be sufficient.
More ›