sbergot

13 ms·

121.
by sbergot 5y ago
In case you haven't seen it this is an explanation that is worth reading: https://adamwathan.me/css-utility-classes-and-separation-of-...
122.
by sbergot 5y ago
The author of the message is BurntSushi. I have seen him communicate multiple times before and he seems to be a reasonable and intelligent person. I cannot imagine that this action is frivolous.
123.
by sbergot 5y ago
> Maybe they thought that it was clear that they had the authority to move member projects to GitHub Enterprise. Seeing the various owner reactions this was obviously not clear for them > Maybe they thought that moving to GitHub Enter
124.
by sbergot 5y ago
I don't understand how asking for priviledges first and taking them anyway makes it better.
125.
by sbergot 5y ago
Projects were moved to the .net foundation organization. The .net organization obtained administrative authority on those projects without asking or notifying their respective owners.
126.
by sbergot 5y ago
Joining something does not mean automatically mean giving them authority on your work. Reading this page: https://dotnetfoundation.org/projects/submit > The .NET Foundation uses either an assignment model or a contr
127.
by sbergot 5y ago
I don't know. "We should have asked the project owners before moving their projects". Why did this lesson had to be learned? This seems so naïve it is hard not to interpret it as dishonest. There must be an explanation on why
128.
by sbergot 5y ago
> it seems that the foundation simply considered the projects as "theirs" in some key ways This seems like the core issue. But I disagree it is a simple mistake. "Oops. I simply considered your work as mine. Sorry my bad!
129.
by sbergot 5y ago
At this point taking responsibility would mean changing the board members. There is no way the .net foundation can have any trust with those members. I am not sure that the .net foundation can still be relevant for anything after this.
130.
by sbergot 5y ago
Macron presented itself as the "reasonable" option between classical left & right & the extreme right. He seems in a pretty good position as far as poles go. The left will be divided as usual. The right is struggling to fi
131.
by sbergot 5y ago
Until today the switch was a good option for indie games. But now the steam deck is going to eat a big chunk of that cake I think.
132.
by sbergot 5y ago
I have a gaming PC and a switch. I buy and play lots of indie games. Each time I have to pick a platform. Steam: more support, lower price, won't have to buy it again if another "version" of the hardware comes out Switch: por
133.
by sbergot 5y ago
Fun trivia: vscode uses ripgrep for its search feature
134.
by sbergot 6y ago
Youtube and chrome are still largely dominating their market. Can you expand on those?
135.
by sbergot 6y ago
> Your job is to deal with customer requirements (i.e. listening to people), and translate those into code other engineers (communicating with people) need to maintain, on a priority/schedule your management (also people), create to
136.
by sbergot 6y ago
"The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." If you are using some js library with the MIT license in your frontend then you are distributing a co
137.
by sbergot 6y ago
Webpack definitely keeps the license headers even when minification is on. They have to start with something like "@license".
138.
by sbergot 6y ago
Webpack keeps the licenses when outputting bundles. Given the popularity of this tool a lot of people are respecting the attribution clause.
139.
by sbergot 6y ago
You can try this with typescript 4.1 : interface User { name: string; age: number; } type CapitalizeProperties<T> = { [Property in keyof T as Capitalize<string & Property>]: T[Property]; }; type CUser = CapitalizeP
140.
by sbergot 6y ago
I think I will always struggle to understand the popularity of the term serverless. From the two definitions found in https://www.sqlite.org/serverless.html classic serverless --> "embedded database" exists and
141.
by sbergot 6y ago
You can initialize your object with main. But if you are reusing some implementation in multiple object you will start to repeat yourself a lot in the initialization. A DI framework allows you to set conventions to avoid repeating yourself
142.
by sbergot 6y ago
I agree with the sentiment. But in order to build something that lower the barrier to entry you need an incentive. Building tools is hard and costly. Maintaining them even more. In video games you have blueprint systems because the economy
143.
by sbergot 6y ago
People use whatsapp groups a lot. Also sharing images doesn't work well with SMS.
144.
by sbergot 6y ago
I have used them on a medium project. I enjoy them very much but I have seen a lot of people struggle with the "rules of hooks"* I can see why some people prefer to use classes where the design is cleaner (even though you are more
145.
by sbergot 6y ago
In my world a company probes the market continuously to see what the market wants. The business analysts are getting a stream of requirements and then design new features. Then devs implement those features. Development stops when market gr
146.
by sbergot 6y ago
Using tailwind is mostly like using css. It is just a selection of recommended properties and values that hides almost nothing about the nature of css. The abstraction is very thin and its main goal is to limit the "power" of css
147.
by sbergot 6y ago
I would say it is the opposite. Beyond a certain project size, semantic html + css becomes unmaintainable because you are not able to predict what while change if you remove one line of css.
148.
by sbergot 6y ago
Come one. This "pitch" is heavily contextualized. Interpreting it as "all best practices are bad" is not very charitable.
149.
by sbergot 6y ago
...because they don't compose as well? But you are correct. The idea of functional css libraries is to go back to putting presentational information in the html. And the justification is that it is a better approach when you are buildi
150.
by sbergot 6y ago
Scoping is one part of the problem. Complex selector is another one. Design consistency is yet another one. Tailwindcss is solving those 3 issues.

More ›