namelosw

75 ms·

571.
by namelosw 7y ago
I'm not sure if it's still an 'interface' since it's compiling another language to imperative code which operates DOM API. So it requires other platforms implements a similar imperative API surface as DOM.
572.
by namelosw 7y ago
I thought this was well known years ago. A better description for VDOM should be 'It's not fast, and is not slow either'. But frankly, what I see in virtual DOM is not about speed. It's a declarative interface, an abstra
573.
by namelosw 7y ago
I get your point. Even without message passing, just in process calculation in Erlang/Elixir is also pretty slow compared to Java. But in the domain of Web programming, scheduling efficiency is much more important than the speed of exe
574.
by namelosw 7y ago
This is really cool. Meanwhile, it also shows Elixir itself is already really fast for the rest of us. Unless you're Discord or WhatsApp.
575.
by namelosw 7y ago
Additional (additional side-note): 'Winne the Pooh' movie has been banned[0] [0] https://www.theguardian.com/world/2018/aug/07/china-bans-win...
576.
by namelosw 7y ago
When I interview other people, I usually ask one question that is really hard for the candidate. I don't expect an answer, I just expect the candidate would give an honest answer. Then I'm always surprised there are so many people
577.
by namelosw 7y ago
Sure, modern Java micro-services could be fast. Compared to legacy Java micro-services to years ago. It's still not comparable with Rails. Let alone some niche bleeding edge technologies which are focused on productivity.
578.
by namelosw 7y ago
We use fluentMigrator for .Net, but basically the workflow is similar to Rails migration. It is working fine and did not slow us down. What slows us down and related to this topic is cross-database migrations. We have a bunch of microservic
579.
by namelosw 7y ago
I always have negative opinion on SQL but I can bear with it by just using a subset. Most of complex stuff are handled in application rather than SQL. Just use it as a simple data store. I think Datalog is a better alternative. However, for
580.
by namelosw 7y ago
Microsoft is really changing fast, it seems. In developers experience perspective, this is really a good start. It's really painful to work with Windows+.Net stack currently. For example, most of the windows menus don't let you se
581.
by namelosw 7y ago
I work on a project consists of tens of devs that continuously delivered applications for almost a decade, and I joined this team 3 yrs ago. At some peaks, there were almost a hundred people. We still continuously deliver new features to th
582.
by namelosw 7y ago
IMO this is the best approach for most scenarios. 9 out of 10 it's lightweight enough and powerful enough. ORMs tries to hide the impedance mismatch, but the underlying paradigm is still relational, which always leads to a leaky abstra
583.
by namelosw 7y ago
Gatsby + Org-mode plugin.
584.
by namelosw 7y ago
And the Erlang virtual machine named beam.
585.
by namelosw 7y ago
That depends on what problem or code base you are working with. The debugger is the best answer when you are working with bad code, which you cannot reason about the code locally -- a random bug only happens on the production env, a mutable
586.
by namelosw 7y ago
> That “static types” are, at their core a tool for writing and maintaining computer-checked proofs about code > That “dynamic types” are, at their core, there to make unit testing less tedious, and are a tool for finding bugs. They a
587.
by namelosw 8y ago
In China, most of the solution would be cut down after days/weeks/months. Although the connection was encrypted, GFW would still try to guess if the connection behaviors match some VPN features according to some algorithms, then c
588.
by namelosw 8y ago
If I get this correctly, both this and Blazor are handling most of the UI logic in front-end, despite they are WASM. So WASM is just another bytecode encoding that relatively smaller than JavaScript, without solving the problem from the roo
589.
by namelosw 8y ago
Yes, CSS modules is pretty good. But most of the CSS-in-JS solutions could let me omit an extra loader since they're just JS.
590.
by namelosw 8y ago
No what I mean by move something I mean adjust HTML structure, and deeply nested stylesheet means less flexible code. You can move anything within a BEM block without breaking style, instead of couple the CSS and HTML structure, which doubl
591.
by namelosw 8y ago
There is, at runtime browser needs to do extra matching. https://stackoverflow.com/questions/13829959/nested-selector... It's about Less but the same rule applies to CSS and Sass.
592.
by namelosw 8y ago
The biggest thing Sass annoys me is in Node.js environment, I have to choose either node-sass which depends on native module which require extra compilation or matched pre-built binary. Or I have to choose ruby-sass which depends on a globa
593.
by namelosw 8y ago
Nesting is bad, because moving any element would break your style. And there's also performance impact. I found scoped css like component or BEM just make sense, which only encourage you nest one level in block namespace.
594.
by namelosw 8y ago
I always believe the exact same thing. Immutability and dynamic typing make it perfectly suited for BEAM. BEAM is also more suited for Clojure. Less powerful CSP and awkward component would be replaced by the actor and supervision tree.
595.
by namelosw 8y ago
My favorite hobby is playing video games. And programming could be 2~5th position on the hobbies list. Every time I think about this, I would be so glad I chose to be a programmer, instead of a pro gamer. Now I can imagine how I would liter
596.
by namelosw 8y ago
Designs like Java which have NullPointerException simply ignore null. Modeling T instead of T | null is just too convenient. It's a lazy design. I'm fine with most of those new ways of error handling, although some feel better and
597.
by namelosw 8y ago
I want to say Any sufficiently complicated REST API contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of GraphQL API. Although complex, GraphQL (done right) is much easier than REST (done right).
598.
by namelosw 8y ago
There's 3kb Preact with almost identical API.
599.
by namelosw 8y ago
The OO languages we are using should be called class- oriented instead object-oriented.
600.
by namelosw 8y ago
I think for Phoenix it's quite easy to deal with unless the project requires a lot of Erlang/OTP stuff. If it's just plain old request/response styles website (I think most of the project falls into this bucket) if you c

More ›