kangoo1707

21 ms·

1.
by kangoo1707 6y ago
I always use Nuxt by default for new projects, and it's a correct decision every time. People who choose to do Client Side Rendering (SPA) finally struggling on SEO and other tasks. 1. Nuxt can runs in SPA mode just like using Vue CLI.
2.
by kangoo1707 6y ago
Why are people slapping Static Site Generators to all the problems? Imagine you build an e-commerce website that has ten thousands of products, that can be accessed by example.com/products/{product-slug}. Now what is making more s
3.
by kangoo1707 6y ago
When dealing with large tables with searching + sorting + paginating capabilities, I always use query params and let the API do the heavy lifting
4.
by kangoo1707 6y ago
And what is the best solution? Client Side Rendering is worse, because users see a blank page until the script is parsed. 100KB is actually desirable, because it's included Vue and Vuex out of the box.
5.
by kangoo1707 6y ago
All browser processes 100KB of scripts just fine. And they process the scripts in the background. The HTML is already parsed and displayed.
6.
by kangoo1707 6y ago
Nuxt works fine for all the uses case that I have come across, even for ERP projects. With Nuxt you can have real redirects, real 404 pages, and a well-established project structure. The only hard thing is that server-side error is more dif
7.
by kangoo1707 6y ago
Phoenix too
8.
by kangoo1707 6y ago
No native support for concurrency operators, no real event loop implementation, lack built-in support for non-blocking IO... I do Elixir regularly and Actor Model is not something PHP developers know
9.
by kangoo1707 6y ago
Not at all. I have worked with both for a long time and I can clearly see the differences. They are used for different purposes. The people comparing any PHP frameworks to NextJS have not been very experienced with frontend development, IMO
10.
by kangoo1707 6y ago
still, no proper multithreading, in comparison with Java, C#, Elixir...
11.
by kangoo1707 6y ago
no PHP framework is similar to the thing that NextJS/Reactis doing. The output is the same (well, isn’t the point of web framework is to spit out HTML?) but the methodology is totally different.
12.
by kangoo1707 7y ago
Please take a look at my CV. I'm a fullstack developer (Elixir, Node, PHP, React, Vue, Flutter...) https://www.dropbox.com/s/kqkm467cb9ay65f/Lam%20Huynh.pdf?dl...
13.
by kangoo1707 7y ago
+1 for Ecto, the most powerful ORM that I have seen so far (among PHP, Node, Ruby, Python and Elixir)
14.
by kangoo1707 7y ago
Exactly, I don't get why people are against it. All ORM allows you to write raw query and using ORM does not mean that you suck at SQL or vice versa.
15.
by kangoo1707 7y ago
SSR can be used with React (NextJS), Vue (NuxtJS) and Angular (Universal Angular).
16.
by kangoo1707 7y ago
More plastic but it's easy to clean - recycle. At least more delivery = less traffic, less polution
17.
by kangoo1707 7y ago
Server-side rendering is the best front-end architecture at the moment. Superior first content paint and is better at SEO than SPA, and have a better architect than MVC. So in what way does if differ from traditional MVC? In MVC, the final
18.
by kangoo1707 7y ago
Use both. Many of the business logics are just as simple as query by id, filter/sort by a couple of columns. A smart ORM will handle fetching relationships without hitting N+1 problem For advanced queries, you can write raw SQL The way
19.
by kangoo1707 7y ago
At my PHP-shop company, most projects are limited to MySQL 5.7 (legacy reason, dependency reason, boss-likes-MySQL reason...). They are all handicapped by MySQL featureset, and can't update to 8 yet. If they had used Postgres some year
20.
by kangoo1707 7y ago
Nesting is okay for one-level. However it violates the principle of least astonishment. How come a button inside .header differs from the button inside a .footer, then where are the differences defined, inside the button.scss or header.scss
21.
by kangoo1707 8y ago
A portion of Vue projects are not single page app: it can be used on top of a server-rendered frameworks like Laravel, Rails. Even the document mentions using Vue by a script tag inside the HTML. This may contribute to Vue being downloaded
22.
by kangoo1707 8y ago
Outside Angular, I have never heard about two way binding as a source of bug
23.
by kangoo1707 8y ago
If you mix server-side rendered apps with Vue, this is the most common way. Second method is to push the data to a window.__data.staffMemberOptions = "{{ foo }}" and use it in Vue.
24.
by kangoo1707 8y ago
I think OP does not mean that Vue is unstructured / non-disciplined. Vue does have a rigid structure and standard though, but it's pleasantly designed and doesn't get in your way. Maintenance has been a breeze for me.
25.
by kangoo1707 8y ago
Not at all, people moves between libraries of the same framework, they will likely refactor jQuery mess into a framework, but it's unlikely for a team to move from React to Vue or Angular (and vice versa).
26.
by kangoo1707 8y ago
JS on both backend and frontend is all about reusability, less context switch and unified toolings. And don't associate less proficient engineers with Javascript dude !
27.
by kangoo1707 8y ago
Do you have any concrete example for "For example, in java, scanning your classes and their annotations to generate code for them at compile time is a standardized feature"? Tip: in JS, I don't want OOP class. If you really w
28.
by kangoo1707 8y ago
then write a method for it. Instead of v-if="currentUser && currentUser.id && ..." you can just write v-if="canDoStuff(currentUser)"
29.
by kangoo1707 8y ago
Where Vue is better: 1. Template syntax. While this is just my own preference, my Vue template is 20% shorter than JSX equivalent, mostly due to fewer brackets and better HTML's class support. 2. Computed property: this is so cool and
30.
by kangoo1707 8y ago
It can be use for form validation. If user doesn't enter an input, we can "wiggle" it for 2 seconds (together with a red error message). Recently I did just that :)

More ›