jupp0r

33 ms·

511.
by jupp0r 3y ago
vscode is an Electron app and is great and more responsive than its "native" competitor apps from JetBrains.
512.
by jupp0r 3y ago
Teams is just a horrible product overall. It wouldn't be better with a completely native app.
513.
by jupp0r 3y ago
Can it inline quote emails properly on MacOS? The regular outlook client was still unable to do so in 2022, last time I tried. I have no idea why people would like Outlook, it's an inferior experience compared to other email clients an
514.
by jupp0r 3y ago
Have you ever heard of APIs?
515.
by jupp0r 3y ago
If they think that this is good allocation of their resources, why shouldn't they? (rhetorical question, it's because remote workers are not 2h of commute time per day less productive).
516.
by jupp0r 3y ago
I agree with you that it's not realistic, but you understand the point I'm trying to make. In the end of the day you are taking a pay cut with this. With a one way 1h commute and 8h of work it's a 20% pay cut. I'm not su
517.
by jupp0r 3y ago
Google Maps directions from home to office printed out and emailed to payroll.
518.
by jupp0r 3y ago
It depends on what exactly the ORM offers as a feature set. ActiveRecord scopes in Ruby for example do exactly that.
519.
by jupp0r 3y ago
Companies who mandate return to the office should pay employees for the additional commute time at their hourly rate. If this becomes too expensive then productivity gains from being in the office are apparently not worth it.
520.
by jupp0r 3y ago
You are assuming that they see high attrition of their best talent as something bad. Sometimes they don't seem to care if the numbers in Excel look good.
521.
by jupp0r 3y ago
> Ford has previously said it is also hiring in some areas, so it’s not clear if these layoffs will result in an overall reduction in Ford’s workforce in the United States or Canada. This might mean that they are eliminating positions, b
522.
by jupp0r 3y ago
Exactly, in my opinion, separating your business logic from your data access layer completely is futile. You will need to either have business logic in your data access layer or fine grained query controls (when to add a filter clause, when
523.
by jupp0r 3y ago
In any sufficiently complex application, something like a query builder that allows different parts of the application to work together to lazily compose queries (vs combining/filtering/sorting the data in memory) will be created
524.
by jupp0r 3y ago
The problem is that people do not want to live in densely packed high rise buildings with noisy neighbors, lots of crime and no nature for their kids to play in when the alternative is a nice little house in the suburbs or in a small rural
525.
by jupp0r 3y ago
I still have to see any super dense city that is actually a good place for families with small children. This is for the reasons you mentioned but also for others like like lack of living space, nature, transportation for the purpose of tra
526.
by jupp0r 3y ago
You could also have mixed use of buildings, putting residential on the outside and commercial on the inside.
527.
by jupp0r 3y ago
I don't get your point. If there's no demand for office space anymore, who will have offices in these buildings? If nobody has offices in them (or if rent is not enough to maintain the buildings), what will happen to them?
528.
by jupp0r 3y ago
There's a sizable chunk of people who think that the concept of inheritance for code sharing is causing more harm than good overall. These languages make it hard to do inheritance for exactly that reason.
529.
by jupp0r 3y ago
Just because something is easy to understand at first does not make it suitable for designing maintainable software. I can understand the concept really well and it sounds completely appealing. When digging through the 18th code base with 1
530.
by jupp0r 3y ago
Agreed, I think it's been a hype at the beginning of OOP, then got overused in Java in the 90s and subsequently taught to every CS college student and it kind of stuck because in college, you don't get to maintain large software p
531.
by jupp0r 3y ago
The ability to reason about code as you are reading it is not only important to "lowest performers".
532.
by jupp0r 3y ago
State can also be shared and reused together with functions operating on it - via composition.
533.
by jupp0r 3y ago
The way I'm thinking about it (just a different expression of the exact same thought) is that inheritance as a means to share code is bad, while inheritance as a means to leverage polymorphism is good. Polymorphic classes can still sha
534.
by jupp0r 3y ago
It's weird that so much of OOP back then was centered around deep class inheritance hierarchies as a means to share code when my favorite more modern languages (Rust and Go) intentionally leave out this part of OOP (thankfully, imho).
535.
by jupp0r 3y ago
Knizhnik made these variables thread local, which is fine if you have a fixed association of threads to data. This looses some flexibility if your runtime needs to incorporate multiple sessions on one thread (for example to hide IO latency)
536.
by jupp0r 3y ago
The problems it causes for Postgres are outlined in the article on LWN.
537.
by jupp0r 3y ago
Can you explain how having a global variable is more performant than passing a pointer to an object as a function argument in practice?
538.
by jupp0r 3y ago
Discrediting my argument by labeling it as ideology and by implying that "blanket statements are always bad" is a logical fallacy that does not touch the merits of what is discussed and I would argue that your argument instead of
539.
by jupp0r 3y ago
Databases are great, especially those who do not use global variables in their implementation.
540.
by jupp0r 3y ago
Please don't use mutable global state in your work. Global variables are universally bad and don't provide much of a benefit. The number of desirable architectural refactoring that I've witnessed turning into a muddy mess bec

More ›