225 karma · joined February 5, 2012
It’s constantly wrong about the simplest things. Just now it was hallucinating about CSS grid properties.
I’m convinced that how good AI seems is inversely correlated to someone’s knowledge in that domain, as you also mentioned.
Still super useful in my day to day but I have to hand hold and correct it constantly.
`useHookAtTopLevel` is especially confusing since other React hook rules are on, and `eslint-plugin-react-hooks` defaults its analogue to "error".
But yeah, no linting in the editor was kinda bonkers.
Bums, I don't meet 2/3 reqs.
FWIW, the problem you’re talking about isn’t one I’ve encountered very often at most of the companies I’ve worked at, and I’ve worked at small startups and large enterprises. I genuinely wonder why that is.
2. The GraphQL spec tells you how errors should be handled.
No one is forcing people to use React, Svelte, Vue, etc. The sentiment of wishing for a simpler time has never felt right to me, cause no one is policing what people use. If you feel like people are forcing you into frameworks, I’m sorry, and I feel like I have a piece of advice.
If you truly believe a framework isn’t worth it, tell your team why. You might be right, and you might be wrong.
I’ve worked at large and small companies; discussions about what technologies to use have always been welcome. I’ve advocated for and won when making a case for “simpler solutions,” when it makes sense.
All that said if you think using a framework framework === complexity for the sake of complexity, you’re wrong. OP I’m not saying you think this, but I have to imagine that it’s the sentiment of at least part of the folks who made this the top comment.
I remember some people taking a little longer to adopt them either cause it wasn’t necessary or cause it didn’t click right away, but eventually everyone learned how to use em, and no one complains about them cause they’re just a tool you use if you use React (which is the framework of choice for most companies).
Honestly, the reaction I often see from HN around most frontend topics usually doesn’t match what the frontend and full stack devs I interact with regularly are saying. Don’t get me wrong, it’s not like we all love React and want to switch state management libraries every week; it’s that React is fine, the ecosystem is fine, and we specifically don’t use every library that comes out week after week.
Do people really like being pandered to this much?
I.e. If you click the question item (but not the blue button), the question is visible on the right. If you click the blue button in the list, the question goes into reorder mode. Those two things are separate from each other, so you can reorder a question that's not currently active.
The solution we ended up with, which is similar to the OP, is what we affectionately called Pick n Plop. I.e. you select an item, the UI tells you where it can go, and you click again to place it. You get keyboard accessibility for free since it's just buttons.
Demo right here (sorry for the terrible quality): https://giphy.com/gifs/9KgZorKdwdsaolomxS/fullscreen
Kyle mentioned this project he's been working on (Github[2]) which aims to add type checking at both compile time and runtime. Curious what you all think about this project, and its merits of downsides over vanilla JS or TypeScript.
[1] https://devchat.tv/js-jabber/jsj-438-you-dont-know-js-yet-wi...
I totally get that it's on me, but things [like this](https://hackernoon.com/how-we-spent-30k-usd-in-firebase-in-l...) happen, and I'm way more apprehensive of services that make that a possibility. E.g. I'd love to use Auth0 for everything, but the risk of spending way too much on something I can roll myself is always on my mind.
I love a good spin class, but like my setup just as much. I can also take my bike off the trainer and ride it outside.
Just made this bookmarklet so you don't have to install any extensions -> https://codepen.io/dgca/full/BmNdmy/
javascript:(function()%7Bwindow.location.href %3D 'https%3A%2F%2Foutline.com%2F' %2B window.location.href%7D)()
It'll open the article using https://outline.com/. E.g. https://outline.com/xX7xe3^ helped me understand what changes are coming.