Eric Fortis

923 posts

Eric Fortis banner
Eric Fortis

Eric Fortis

@efortis

Frontend Developer

Katılım Aralık 2008
1.3K Takip Edilen220 Takipçiler
Dave Jones
Dave Jones@eevblog·
I've been looking at cars on the road. Why are there no visually asymmetrically designed cars? Apart from functional reasons (exhaust port, side opening tailgate, number plate etc) all visual design elements are symmetrical. Yeah, yeah, I know, humans like symmetry, asymmetry is branded ugly. But why so few examples of it and so many companies unwilling to rock the design boat? Are us humans that wired to symmetry that it's impossible for an asymmetrical design to be successful? Only major production example I can think of is the Nissan Cube, and they only did it because it's part of the functionality of the side opening tailgate.
Dave Jones tweet media
English
42
0
35
5.1K
tara_
tara_@TechByTaraa·
as a developer, what do you prefer for frontend?
tara_ tweet media
English
101
6
181
12.9K
David Cramer
David Cramer@zeeg·
What’s the best IDE right now that isn’t full hands off to agents, but integrates them extremely well? I need to rewind time a bit and stop wasting it
English
106
2
161
102.5K
Eric Fortis
Eric Fortis@efortis·
Tailwind Eye. My plugin for WebStorm for folding TW classes and visual fading non-TW bits, for context switching without much clutter. WIP. $2.80 in tokens so far. 95% vibe-coded
English
1
0
0
45
combab0
combab0@combab0·
@DavidKPiano I'd like to learn what the "right way" looks like in practice. Could you recommend a few open source projects that you think follow this approach well?
English
1
0
0
442
David K 🎹
David K 🎹@DavidKPiano·
This is the right way to go for most apps Stop baking app/biz logic into the UI layer; it's only convenient short-term And stop calling separation of logic "over-engineering" - it's just regular engineering
Mario Zechner@badlogicgames

People of pi. I'm going to break the extension API hard. Specifically, business logic (event handlers, custom tools/compaction/etc.) needs to be split off from the ui layer. it will likely not be a massive amount of work to migrate an existing extension, but it will hurt a little.

English
8
12
210
22.3K
UI/UX Savior
UI/UX Savior@UiSavior·
Designers who code are the most valuable people in tech 🦜
English
8
15
171
6.6K
IP
IP@ipwanciu·
Put this into your main CSS file; it won't break your app, I promise! 👇 Your customers will thank you!
IP tweet media
English
29
62
1.8K
288.3K
Frontend Masters 💻✨
Frontend Masters 💻✨@FrontendMasters·
The React docs pushed everyone toward Next.js/Remix, but most of us aren't at Facebook scale. Client-side React is still 100% viable. Use the right tool for YOUR problem. Not every React app needs a framework.
English
5
7
94
6.7K
Mechanical Knowledge
Mechanical Knowledge@mechanical_4u·
The Tool That measures circles in seconds
English
25
68
753
56.2K
Eric Fortis
Eric Fortis@efortis·
@ash_twtz @vivoplt yep, also because (1) they use a non-optimal compression levels, because (2) they compress at runtime, which is slower too. on the other hand, e.g., with nginx you can pre-compress static assets
English
0
0
0
52
Vivo
Vivo@vivoplt·
Interviewer: CDNs make websites faster. Then why can a CDN sometimes make your website slower?
English
30
8
133
29K
Catherine
Catherine@catherine_6907·
She's not wrong
English
426
298
11.6K
6.7M
Javokhir Rajabboev
Javokhir Rajabboev@javka1214·
@efortis @DavidOfMesa @MozDevNet This is literally worse, why would you refactor it? async/await is better and I don't see any benefit or meaning from your refactor other than introducing bugs blindly
English
2
0
1
39
Matthew Phillips
Matthew Phillips@matthewcp·
Why do people want their client side router to be a component? It makes everything you do that's not rendering so weird. Like side effects. Router API design was solved long ago, they're callbacks. Just do callbacks.
English
6
0
14
3.1K
Guillermo Rauch
Guillermo Rauch@rauchg·
I started the @nextjs you know today from a 𝚁𝙴𝙰𝙳𝙼𝙴.𝚖𝚍 specification. That was the singular commit that set it on the trajectory you see today. We proceeded to furiously write code for weeks as we saw a unique window to disrupt the React ecosystem, which primarily consisted of "boilerplate" repos and static-only tooling. I now believe most software (and companies) will start out as markdown files, but it's agents that will be doing the furious coding. And the releasing. And the maintenance. I'm pretty happy that the API we laid out is as relevant as ever today. It's simple, filesystem focused, and its principles remain unchanged. v0-nextjs-hello-world.vercel.app
English
72
38
1.2K
189.1K
David Neil
David Neil@DavidOfMesa·
@efortis @MozDevNet I think you've introduced two bugs. api.getState won't have "this" bound. And "response.ok" is no longer being checked.
English
1
0
1
413
Marko Denic
Marko Denic@denicmarko·
CSS tip: Stop duplicating your CSS for Dark Mode. The new light-dark() function lets you define both values in a single line. It eliminates the need for redundant media queries and keeps your variables in one place.
Marko Denic tweet media
English
24
83
649
26.5K