Retozi

6 ms·

1.
by Retozi 6y ago
we use jooq extensively it's probably the most valuable tech in our backend. Also among various other tech stacks I've never seen something that hits the sweet spot between "plain sql" and "advantages of ORM-stuff&q
2.
by Retozi 7y ago
I have never understood why typed languages make you slower at any point in time (early, late etc.). Because you have to hit more keystrokes to write your program? That doesn't compute. typing is the thing you do the least amount of wh
3.
by Retozi 8y ago
I'm personally in the "functional handler" way of doing HTTP Request camp. We have a very small Ktor service in Production, and it works nice, for legacy reasons, we're using http://sparkjava.com/ for th
4.
by Retozi 8y ago
Frontend: (vanilla) React with TypeScript. - TypeScript is more important than React, static typing is such a productivity boost, even for projects of all sizes. - Start with vanilla React and create-react-app, monitor for painpoints and lo
5.
by Retozi 9y ago
I agree. I exlusively write React Frontends since 2014, and very minor things have changed. It feels a lot more stable than before, where every project had homegrown framework stuff on top of backbone.js or jquery, or then using ember.js. T
6.
by Retozi 9y ago
This is a quite common myth that is factually wrong. It's the main way for a private wealth advisors to talk somebody into a unecessary mortage. The interest rate on mortages is always higher compared to the interest rate on leverage f
7.
by Retozi 9y ago
I agree 100%. TypeScript is an invaluable, mature technology that provides large productivity boosts to any team that maintains a mid-sized code base. It plays extremely well with React too, and it's benefits are independent of the tec
8.
by Retozi 10y ago
I'm using a MacBook Pro with Windows on it as my main development environment except for iOS native stuff obviously. 1. install chocolatey https://chocolatey.org/ , and install everything with it 2. install conEmu for a
9.
by Retozi 10y ago
I like it as well. I have yet to see tech stack that has comparable potential but is less complicated and can be stripped down as low as the web stack if your requirements permit it. I mean yeah, if you have a big app, complex requirements,
10.
by Retozi 10y ago
These are a lot of tedious to write tests in a frontend codebase that mainly renders a lot of state into HTML. Additionally, these are tests that you will have to tediously adjust every refactor since HTML frontends and it's data APIs
11.
by Retozi 10y ago
TypeScript is the one technology I would discard last of the entire web stack. Using TypeScript instead of JavaScript is such a productivity boost for a team developing a sizeable single page application, any other technical decision (which
12.
by Retozi 11y ago
I believe what he is trying to say is this: It will take a person a couple of days to "grok" Redux, and a quite a bit longer to fully understand the ins and outs so one can make informed, confident decisions on how to solve proble
13.
by Retozi 11y ago
Not every application faces all the problems you mention: A lot of teams don't have the "designer" problem and are just fine without JSX. Passing data through dozens of children is not a problem in every application, a lot of
14.
by Retozi 11y ago
For anyone that has the ability to pull off a project that needs seperate state management. It's really just a days worth of looking at the original flux, redux and other implementations and figure out what's best for your team an
15.
by Retozi 11y ago
I agree with your argument. I have seen people say on HN that 1 hour of setup to start a project is too much. If this is the case, React + stuff is really not the right thing for you. However, the React ecosystem is really not that complex.
16.
by Retozi 11y ago
you can use the functional way of setState by passing a transaction function (state: State) => State . This allows for typed, immutable updates since the function gets passed a copy of the state. If you need an object (say to use it in s
17.
by Retozi 11y ago
I really don't understand the underlying complaint of your comment that the React ecosystem is in constant flux (see what I did there?) I've been writing React SPAs for roughly two years now. Very few things have changed. The firs
18.
by Retozi 11y ago
From my experience, it is not about the FRP kool-aid. It's about the robustness of the concepts of React (DOM diff-ing, favor immutability, declarative views etc.) Adopting something like elm might have its advantages, but also comes w
19.
by Retozi 11y ago
It is my main IDE for Typescript since v0.1. VSCode in combination with TypeScript provides a superior Frontend-Dev experience to any other Language - IDE combination in my opinion. Apart from an occasional restart required it has been pret
20.
by Retozi 11y ago
I have written a full production application in CS before switching to JS and then eventually migrated to TS. I was one of the "you save characters, you gain readability" proponents as well (I love Python too). However, it is a te
21.
by Retozi 11y ago
Does it matter though? As of today, it is incredibly hard to evaluate frameworks because you generally only have the time to evaluate small examples, but those are usually easy to do anyways. This thing here is as tricky as it gets for the
22.
by Retozi 11y ago
This is great! In my opinion, this should not only be a challenge for Flux frameworks, but generally replace todoMVC as the "go-to" example implementation. This should reveal potential pain points a lot better.
23.
by Retozi 11y ago
http://fightland.vice.com/blog/joe-rogan-gsps-alien-abductio... he mentioned it here originally: https://www.youtube.com/watch?v=rmFsUV5ICKk his theory is that he was abducted by aliens, but it sounds
24.
by Retozi 11y ago
One might argue that MMA crosses the line in terms of acceptable injury, but it would be quite unfair to single the sport out as "the sport that crosses the line". Boxing, Kickboxing and Football are arguably as bad as MMA in rega
25.
by Retozi 11y ago
I think this is a bad idea. First with methods, you have mutable state, which I believe should be avoided. It causes a lot of problems for efficient rendering. You could make some kind of wrapper, but I guess it's not worth the hassle
26.
by Retozi 11y ago
It is a fantasy. Regarding the sparring between BJ Penn and her, it somewhat confirmed that he held back. See https://www.youtube.com/watch?v=g8TBlo3yPUM#t=51m11s There are various other videos of her rolling with other men
27.
by Retozi 11y ago
In my opinion it is a misconception that React "mixes" representation and logic. You can _implement_ both representation and logic with React. (instead of JS for logic, and some clunky template language for representation). This d
28.
by Retozi 12y ago
Ex-Coffeescript ,now Javascript with lot's of Python experience guy here. The "I understand CS code much quicker" argument is a valid one theoretically, but In my opinion, it does not hold up practically that well. CS got one
29.
by Retozi 12y ago
1. Stores can contain more than one "model", they cover a certain "domain" 2. Stores contain immutable data. This allows for reference equality checking which will yield performance gains 3. Stores do not contain asynchr
30.
by Retozi 12y ago
I feel like these somewhat restricting patterns can increase your productivity massively. If your app fits the restriction. If not, it will slow you down. There is usually not enough emphasis on the nature of the app in these X vs Y framewo

More ›