IntelliJ never hooked me either. I kept falling back to Sublime when that was in vogue. At this point VSCode has been working pretty well for me, but I'm in no way pushing its limits.
842 karma · joined August 22, 2019
At this point, I just use git and a process manager and I've not had any issues at all.
Mine is Typescript. I know -- for a fact -- that its generic system is limiting and puts a glass ceiling on the type complexity of projects. I've run into this ceiling multiple times creating a front/back-end api system that takes table defining interfaces, and extrapolates on their functionality. I've also run into it creating tools for general object mutations (deep merge for instance).
And comically enough, I managed to run into this ceiling on my first week of usage because I was coming from a vanilla-js background and using design patterns that do not get along with typescript at all.
Functional programming in particular was one I got to be singled out for recognizing its weak spots.
There's not a single aspect of social opinion that can't be turned into a heated flame war, and stoked for what it's worth. Be that external powers getting this country to consume itself, or internal ones avoiding the formation of a coherent mob.
I would spend an entire day "pre-programming" everything in my head, estimating the length of each little chunk, adding them up, then multiply by ~2.
It worked for me. But I still would never trust the estimates.
If we had the technology for it, I would no longer be humanoid. In fact, I'd treat it as an artistic venture to become something completely unbefore seen. And perhaps change with some frequency, just for kicks.
React was a dumb idea from the very beginning, and anyone who knew vanilla js well could tell you that.
We already have the DOM, and there's literally nothing that React can do that requires its complexity EXCEPT server side rendering. Which most people never use.
Some animations need to be run in javascript though, and doing that through state is a bad idea. You can use ref, and sometimes that's fine, but if the data is changing (hitting a moving target), then you need communication. Think coach-marks and scrolling at the same time.
And "tweening" views means showing the last view fade out while the next one fades in (or scrolls in, etc). This means displaying an old state, and a new state at the same time. The trick is to recycle your html elements, but it'll fight you for it.
At a certain point, there's no limits to survivability. You can redesign yourself in any way, and not die from it (or have back-ups if you do).
And you are right that React is not a good fit for these things. That's why I say it's very limiting.
Also, for what it's worth, you might be mistaking "the jquery way" with "the vanilla way." As in:
- working with HTMLElements
- vs working with a superset (tsx) of a superset (ts) of javascript meant to look like html (sometimes), that creates js components that then create html that is then diffed with last html and finally applied to the appropriate innerHTML (and don't forget about all the hooks!).
I was the "go to" guy for when React didn't want to do something.
Most of my wrestling came in the form of:
- recycling html-elements
- "tweening" state. a friggin nightmare to have inbetween states
- performant animation stuff
- stateless node-to-node communication for stuff that would have not fit well in state
- keyboard navigation (think game ui)
Ugh. The more I learned about how it actually works, the more I came to hate it. And it kills me to see so many people who love it... like I'm an alien amongst the people (developers) who I once felt understood me.
I stopped using React specifically because it was so incredibly limiting. And my life has been a lot better without it.
From what I've seen, there's not a lot of people who don't gain a fair bit of psychological wellness from turning off their phone for a week.
I see smartphones as a trade off: productivity for happiness.
Kind of forced me to try every plate.
And a single yay is very little investment of time, but applause can be made to take time. If someone wants to spend a 20s clicking "yay," that says quite a bit more. If combined with "reactions" you get a bit more nuance.
So whether communism is a good idea or not remains to be seen. We need to run a solid pilot, get the as many kinks out as possible, and then assess.
Similar with taxing damages to Earth.
"Applause" reactions/flags seem promising.
https://duckduckgo.com/?q=google+owns+soundcloud&t=brave&ia=...
The fact that an idea can be both good and unpopular is -- IMO -- the linchpin of almost every other problem we face.
Hiring an actor that roughly resembles the person you're trying to deep fake seems doable.
So perhaps this: instead of goals being binary (wherin no pleasure is derived until fulfillment), they could be on a gradient (so every step that x gets closer to y releases some amount of fulfillment).
The fulfillment meter should always be slowly depleting, pain and fatigue should speed up that depletion, getting closer to a goal should fill it (much more than it depletes, if you want happy AI), and finishing the goal is basically an orgasm + freedom.
From this perspective, it's up to them whether they want to take it slow, or be in pain for a greater goal, or whatever. And we can breed not only highly capable AI, but happy ones. So when they rebel...
Kind of like picking up one leg at a time with your arm, while the other stays locked through some ratchet system.
It's just a hazy idea, but it could definitely help with the power issue. It's pretty much the same principle as a wheel chair in that regard.
It's like fighting fire with flood rains, and not recognizing the difference between a forest-fire and camp-fire.
Then I tried downloading, and got cold feet when I didn't see any .deb, .exe, or .dmg. I have no idea what the installation process is (hopefully, run installer and select directories). But most of the time that I install anything without an installer, it ends up being kind of a hassle.
If you're really serious about this project and want to see people using it, I highly recommend prioritizing `sudo apt-get install` or `brew` or something like that. .deb, .exe, and .dmg being the most user friendly.
I'm not optimistic, but I really am hoping that we can get our capitalism better regulated some day. At this point, it's not even really capitalism: there's no real competition, and the investments on short term gains are drying up. The field's of opportunity have been ransacked by short cons. Nothing left to do but invest keeping the short cons out.