daliwali

8 ms·

31.
by daliwali 9y ago
>A number of "engineering" posts are not written as a thoughtful engineer might, and are in many ways marketing for the products sold (like a training program). I think this is a great insight that is often overlooked in tech m
32.
by daliwali 9y ago
There is a lot of FUD from the GraphQL side of this debate, and even overlapping goals with REST. From the article: >With GraphQL, the client speaks a request language which decouples clients from servers. This means we can maintain and
33.
by daliwali 9y ago
>Also is there any protection against pathological requests? (e.g. if there are loops in the object graph, can I build an arbitrarily deep GraphQL query that will take an arbitrarily long time to complete?) I've seen some GraphQL se
34.
by daliwali 9y ago
That's what a vocabulary is for. schema.org[0] has something semantically equivalent to a user, a person. [0] http://schema.org/Person
35.
by daliwali 9y ago
That common framework should be the web platform itself, not the various scripts on top. Hyper-specialization leads to risk of extinction.
36.
by daliwali 9y ago
>because they like it Imagine going to a doctor and getting a prescription because "they like it". >there is a wealth of knowledge on the internet about how to fix every little problem Let's hope they're using the
37.
by daliwali 9y ago
It's expedient for many reasons to use a major framework, but it doesn't mean there are no drawbacks. There are learning curves, inner platform effect (have to do the framework way of doing things), major breaking changes and outd
38.
by daliwali 9y ago
Sorry, I should have qualified it as Single Page Applications, not web apps in general. Still, hard to find a front-end job that isn't about SPA anyways.
39.
by daliwali 9y ago
No one is stopping you from implementing a URL like: `/feed?include=users`, which is easier on the eyes than the GraphQL equivalent. But clients generally aren't aware of the `include` query or what it does unless it's advert
40.
by daliwali 9y ago
Formal specs[0][1][2][3] have existed for years, not necessarily from the W3C. All of them suffer from a chicken or egg problem. Without servers following specs, there won't be clients. Without spec-based clients, servers will continue
41.
by daliwali 9y ago
Alan Kay was right, programming is pop culture. It's increasingly harder to find non-legacy single page apps that aren't using React or Angular (Vue and Ember are distantly trailing behind). Corollary: it's increasingly harde
42.
by daliwali 9y ago
For what it's worth, I boosted my SAT score by 400 points (2100 out of 2400) just by being more aware of the tricks used on those tests. My weakest subject was writing, but not because I am a bad writer, my handwriting is garbage. It&#
43.
by daliwali 9y ago
>JWT might be the one case in all of practical computing where you might be better off rolling your own crypto token standard than adopting the existing standard. This isn't the first time I heard this claim, but I've also read
44.
by daliwali 9y ago
I think that the main issue is the client must send what is essentially the plaintext password on every request, meaning the client also must store the password. It might be short-lived, might not, but is a security risk to keep the passwor
45.
by daliwali 9y ago
No, the entire API really is one function. The events and animation helpers can be implemented by the user in a few lines of code, they are not at all required. There is nothing stopping you from adding event listeners or CSS classes withou
46.
by daliwali 9y ago
Talking about overcoming "impostor syndrome" is a great way to humble-brag, because it makes the assumption that the person is already competent enough to feel inadequate. If you ask software developers to assess themselves, most
47.
by daliwali 9y ago
This is by the way, a thinly veiled insult. Citing Dunning-Kruger effect is just a way to call someone an idiot who thinks they are competent. Nobody looks at objective benchmarks. My own DOM utility is faster than React.js, and in fact it
48.
by daliwali 9y ago
Sorry, but avoiding templating syntax was really a hard design goal. It may not be a tool for everyone. The reason is that every templating language I've used either is or becomes a Turing-complete language by itself.
49.
by daliwali 9y ago
This has been revised. There is now a separate entry point for helpers, to make it obvious to people who don't read docs, that it is separate functionality: var helpers = require('simulacra/helpers') var bindEv
50.
by daliwali 9y ago
>Astronaut-architects Facebook can come out with a project that's over 40k lines of code, and it is "extremely simple". But no, it is me with my little 5kb function who is the "astronaut-architect". >It's
51.
by daliwali 9y ago
Why would I take comments from disembodied strangers on the Internet on a personal level, or "develop personally" from people replying only to copy and paste verbatim from marketing, doesn't make sense. All I did was write th
52.
by daliwali 9y ago
Developers are generally not rational people who critically analyze the pros and cons of the technologies that they use. Honestly neither am I, I don't make decisions based solely on objective measures or benchmarks for that matter. Th
53.
by daliwali 9y ago
There is actually only one function, that is the one returned from `require('simulacra')`, the others are merely conveniences that are common enough, and `retainElement` is a symbol, not a function. To demarcate this separation
54.
by daliwali 9y ago
I'm not sure I understand what you mean by additional mapping. Here's all that's needed in the template: <div class="city"><span class="name"></span> has <span class="p
55.
by daliwali 9y ago
Minimalist, modern web browsers exist. A good example of this is surf [0], which is based on WebKit and is <50kb of C. That's less than half the size of React source. It obviously doesn't have all the features that Firefox or C
56.
by daliwali 9y ago
Simulacra.js is a single function (!), not much of a library, and very far from being a framework.
57.
by daliwali 9y ago
That describes the DBMon benchmark [0] pretty accurately. It has a hundred "components" (rows), each with several subcomponents that re-render based on state changes. Actually it is less interesting and indicative of mainly one as
58.
by daliwali 9y ago
You missed the first sentence: >A paragraph of well thought out text will be ignored. I don't feel that it is necessary to have to explain in depth why having such a complex architecture for doing a simple task such as manipulating
59.
by daliwali 9y ago
I'm well aware that there must be an element and a selector for that element. But this is exactly how CSS works as well, it's separation of concerns. Only recently have inline styles become trendy , much to my dismay. The total a
60.
by daliwali 9y ago
>I'll bet that React will be a whole bunch faster than whatever DOM reconciliation library you build up from scraps of vanilla JS You don't have to bet, you can verify the results yourself. Look here at these benchmarks [0] and

More ›