daliwali

20 ms·

151.
by daliwali 10y ago
If you are really in a hurry and can't commit to learning the hundreds of forms in Common Lisp, Scheme is a minimalist alternative. The entire language has only a few forms on which make up everything else.
152.
by daliwali 10y ago
How ironic is that comment coming from a throwaway account... Given that both frameworks are products of multi-billion-dollar corporations, used mostly in commercial applications, and keep a fair number of people employed, I think it's
153.
by daliwali 10y ago
Those weren't accessible to begin with, not even back then :)
154.
by daliwali 10y ago
There is probably a non-trivial amount of astroturfing here, but also software developers are people too, and people get dogmatic about their opinions. I probably won't ever use Angular unless I find myself desperate for work and can&#
155.
by daliwali 10y ago
Emphasis on the past tense -- "was" :)
156.
by daliwali 10y ago
Disagree -- the web platform itself is pretty solid. Websites made decades ago are still accessible. The tooling that exists today will probably last much shorter.
157.
by daliwali 10y ago
Spoiler alert: serverless is made of servers. But seriously what they mean is that you rent an allotted amount of resources on a server farm to run your application for a short period of time, and then the resources are freed again. Not all
158.
by daliwali 10y ago
Not sure why one would decide on using a framework because it is integrated with a few vendors that are popular at the moment. There is significant lock-in, and just because it is open source does not make it free. Lots of companies right n
159.
by daliwali 10y ago
There is work on WebAssembly to add DOM support [1] but for now it is speculative. This is the main limiting factor since other languages have to use JS as a compile target instead of WASM if they want to interact with a web page. [1] http
160.
by daliwali 10y ago
Shilling my own library here: http://simulacra.js.org No template syntax to learn, one function API, 5kb gzipped.
161.
by daliwali 10y ago
Hahaha, no. Every time the argument for "maintainability", or some other subjective quality like "readability" is mentioned, another question must be answered "to who?" The class keyword was added a few years t
162.
by daliwali 10y ago
All of a sudden, perfectly working JS becomes "legacy" code due to the introduction of a new feature in the spec. There's that saying, only the software industry is more driven by trends than the fashion industry.
163.
by daliwali 10y ago
The average Snapchat user isn't going to think about the process of uploading a picture to a central server which is then relayed to the intended recipients and then deleted on the proprietary client-side application (which can be work
164.
by daliwali 10y ago
This IPO is yet another indicator of a civilization in decline. Snapchat watches people in their most private, most intimate moments, who are unaware that all of their data passes through centralized servers. Why should states even bother w
165.
by daliwali 10y ago
I think one of the reasons why C became popular in industry and Lisp didn't, is because Lisp is harder to translate into efficient machine code. C was closer to how the hardware works. In the earlier days, specialized hardware was buil
166.
by daliwali 10y ago
I think this article is a big lie, because it's based on the premise that what is being described is in fact REST. First, it has nothing to do specifically with the mechanics of the HTTP protocol. There was an emergent pattern as peopl
167.
by daliwali 10y ago
Nope, just petty politics.
168.
by daliwali 10y ago
They can continue doing what they're doing already: - Suspending accounts for no reason at all. - Shadow banning users by hiding their replies (they refer to certain users as "low quality"). - Aggressive censorship of alterna
169.
by daliwali 10y ago
Of course, I even write some hobby projects in Common Lisp. There are data interchange formats that use S-Expressions, namely EDN[1]. But JSON remains the most popular format for its widespread support, and its few data types map to most la
170.
by daliwali 10y ago
An "idempotency key" as this article suggests applies to WebSockets as well and is particularly useful for correlating a response to a request.
171.
by daliwali 10y ago
>One of the principles of open source is meritocracy — the best idea wins, the most commits wins, the most passing tests wins, the best implementation wins, etc. This is so wrong that it's hilarious. Lots of garbage gets popular and
172.
by daliwali 10y ago
>it's so different and you've added so much work to it With web pages, it's standard and effortlessly handled by the browser. Given a form with inputs specified by the server, a client sends a request with media type appli
173.
by daliwali 10y ago
I am not the authority on what REST is. That would be Roy Fielding, who has explicitly stated that hypermedia is a requirement[1]. So go ahead and tell Mr. Fielding that his definition of REST is incorrect. I am well aware that REST no long
174.
by daliwali 10y ago
The answer to that is really simple: JSON is a widely supported standard in many platforms and languages. Whatever the latter is, is not. What's better than writing a parser for the latter format, is not having to write anything and ju
175.
by daliwali 10y ago
In reply to fixermark, there is also nothing stopping you from very complicated queries in REST. There is not even a requirement that the server must respond immediately. For example I could request: POST /queries With some raw databas
176.
by daliwali 10y ago
>it has become very clear to me everyone has a different interpretation of what REST can or should be This is very true, the term has been abused so much that it has no relation to its original meaning. We can loosely define REST by one
177.
by daliwali 10y ago
>the structure REST mandates. There is no structure that REST mandates, if there were it would be a specification and not an architectural style. There is nothing that says that you can't query for that: GET /comments?sort=vote
178.
by daliwali 10y ago
You are correct that in a REST system, every resource has a "primary key", that is the URL. Where you are wrong is that REST doesn't mandate that a resource can only be accessed by its "primary key". There is noth
179.
by daliwali 10y ago
Easy mode: GET /documents?include=comments Think of how this can be done on a web page. The documents page has a link to follow, "include comments", which links to "?include=comments". The exact query doesn't m
180.
by daliwali 10y ago
What they describe is not REST. Nowhere in this document mentions hyperlinks, a strict requirement of the REST architectural style. The best analogy would be a simple web page, which usually contains hyperlinks that a client can follow to d

More ›