I think HTML is bad. I think DOM based development is bad. I really feel that Desktop UI development is much more mature and has much less legacy to compete with when developing a web UI.
I think the very near future will be web assembly code that paints a canvas. Mature desktop methods with GUI design tools will be ported to web assembler and retrofit for the web. QT5, imgui, are just the beginning.
I think a good exercise would be to open the Full Stack React book again and port the first few running examples to a Qt Quick Controls application and then target webassembler. I am willing to wager that anyone who gives it a real shot will be impressed at the productivity gains -- which generally stem from QML's expressiveness and not having to deal with React's over-complicated design. Not to mention, you'll not waste time because some component you made behaves differently across browsers. You'll also notice a complete lack of the dogma that tends accompany modern JS frameworks and libraries.
It also feels good to know that your UI may be a bit more performant that DOM based UI's.
With QT5 and it's qt quick controls 2, I put together the demos of the first few chapters of "Full Stack React" within minutes. The QT creator helped me with this. I compiled to desktop (which is quicker) and then when I was done I compiled to WASM and loaded it up in the browser.
With React and other DOM based tools, it takes very long to develop even simple GUI's. There are tools like React Studio, but nothing as mature as QT. Also QML and Signal/Slots are much better than React's model IMHO. In addition, Virtual-DOM is a hack that only DOM based models suffer from and adds overhead to the development model.
I think the article is right -- Out with the new, in with the old!
I wouldn't hang on every word of the agile manifesto. For example you don't have to google too much before you find people having debates over unit testing vs acceptance testing in the name of being "Agile" not giving to much attention to the "over processes and tools" part of the manifesto.
Both jumping ship for raises and other things are also true according to multiple sources. Job satisfaction is another leading cause. The tech industry has to fix the issue of turnover, its costing too much money and careers are being diluted.
The first problem with agile is that false dichotomy - "It's either agile or waterfall". Sorry but that dichotomy doesn't exist. Waterfall vs Agile is just a good-bad binary. Surely you want to iterate quickly and stay in constant contact with customers, if that is all agile is then I am all in. However, I can't subscribe to robbing developers of ownership of a domain. I would even do microservice arch if it meant dividing things up into domains and assigning developers microservices that they own. I want to keep developers and giving them responsibility and ownership is a good way to do it.
Its funny because, in Agile you hear "You don't want one developer leaving with all the knowledge" now instead we have all the developers leaving with all the knowledge.
1) Humans are stupid. If we were not were not we would have long ago colonized the solar system. The technology is there but we rather not. We would rather fight, discriminate, and withhold knowledge which would, quite literally, save all of our lives.
2) Programming principles can be understood because they are based on concepts that are largely built upon a physical machine. Math can't really be understood, you just have to become accustom to it. Mathematics is simply too abstract to relate to things you already know like programming is. So when learning maths don't try too hard, just memorize, and familiarize. Once you start thinking you are smart you stop working and you stop learning.
Well, its time to move on from Hacker news. This will be my last post, I will try to get them to remove my account. Suppressing conversation about topics very relevant to technology is where I draw the line. There is nothing political about facts. If the moderators of hacker news can't handle that (because they too are a white male dominated company) then that is just something they are going to have to deal with - even if reality is something they can't deal with.
I guess political nature of the article take precedence over any form of science or tech found in the article. Moving on from hacker news waste of time.
Why not just flag the comments. Why shut down the whole discussion? Seems like a heavy handed approach. I mean of course talking about the rampant racism in tech will make many white males uncomfortable, that the reason we post and talk about it. So that people become more comfortable talking about it. The mods aren't helping the problem they are exacerbating it by coddling.
I'm not sure anybody used the word "racist" except for you. No offense, you seem kind of bitter. Comparing bias in tech to the fact that most NBA players are black is quite disingenuous given 23% - 25% of NBA players are white compared to 2% of tech personnel being black. But based on the content of your post logical reasoning doesn't seem to matter. I can see you in a basement wearing a maga cap and posting on hacker news while alternating between listening to trump rallies and fox news.
While I support something like this, I can't shake the feeling that everything that can be done here can already be done using the features of my desktop or editor (which is Emacs for programming and MS Word other stuff).
I agree with you but just one point - I didn't know African hair is thicker. Do you mean that African's tend to have more hair follicles on their head, or do you mean that the hairs themselves are thicker? I'm not sure if either is true. Do you have a reference.
I think its being conflated because the author thinks they are one in the same and is trying to make the point that they are. I happen to agree with her. However, thank you for the classic white male deflection defense.
> This tends to underestimate other systemic disadvantages that prevent women and minorities from staying in the field, such as harassment, unfair compensation, and imbalances of power.
I worked at a place that made a push to hire minorities (it would seem). However, these minorities would leave faster then they could be hired. If a minority "opened their mouth" they would likely be terminated - only white men were allowed to have an opinion or be passionate. Other minorities would just leave after a few months and the white male leadership would always make happy excuses for why that person left (e.g. "Oh she didn't like X" or "he didn't really think Y worked for him"). In the mean time I sat there and watched as white new hires were coddled and treated well while minorities were gossiped about in the most horrible way if they made what appeared to be even a simple mistake. I say "what appeared to be a mistake" because in these gossip sessions (that conveniently only happened when only white people where in the room) it didn't seem that anyone ever asked the minority anything about the apparent mistake. It was almost like they were trying to convince themselves that the person was unqualified and didn't want to take the chance that they could be wrong - so they didn't inquire in the least.
I could do better with the Ad-lib library I wrote as a freshman in High School. At least those generated comments where coherent. The garbage that is being generated here is an incoherent mess. Deep learning is going to be another blow against the AI community like in the 80's when expert systems didn't pan out. Once ML is well understood a few well defined algorithms will replace all the buzz, just like expert systems.
ML as we know it today is not going to usher in Sky Net.
The term Next-GEN may need to be phased out. We live in an age where Next-GEN is a transparent server update. Hi-fidelity graphics will soon be streamed over the web and game /content producers will write to some generalized platform and upload there games to be streamed. Graphics will improve transparently as servers and games are updated. Gone are the days of the console wars.
Basically, buying your own hardware for console gaming is dead (I don't agree with it but this is where things are going). There may be a PS5 but it will likely fail. Streaming games is the future (however big brother it is).
Sure, its farms. Tell me another one. If yo see who owns all the wealth, it would be about an equal percentage of the population. Stop deflecting from the gross income inequality that exists in UK and across the world. Its a fight that you can't win because the numbers don't support you. (pfss. "It's farms").
> gentrification, which is loosely defined as somebody not like you moving into your neighborhood.
I would say gentrification is the act of displacing poor people for homes that their family lived in for many years, to make way for wealthier white individuals who would like to live in that area.
In a town I lived in a company was made to clean a river and surrounding streams after years of pollution and abuse. The company did a very nice job. Now this town had a bunch of beautiful water front property. Immediately the minorities in the neighborhood were drummed out. It was very sad to see because I knew many of them for years, my sister's (now husband) was from that area, and now they are mostly gone. No body stepped in to protect them. Even the Chinese food store, with the lady that would give me extra candies when I would go there as kid, is gone. I would be gone too, if I didn't live across the bridge in the wealthier area.
Gentrification isn't just "people moving in", its the destruction of the way of life of poor, simply because the wealthy found something they like.
Its all context dependent of course. If you are at a place for three years doesn't mean you can't interview. Three years at an organization is a long time. I've seen people interview after 6 months at an organization. Depends on the organization. Having a person start interviewing people after three years development experience total is probably not a good idea - depending on what you are interviewing for.
I think the very near future will be web assembly code that paints a canvas. Mature desktop methods with GUI design tools will be ported to web assembler and retrofit for the web. QT5, imgui, are just the beginning.
I think a good exercise would be to open the Full Stack React book again and port the first few running examples to a Qt Quick Controls application and then target webassembler. I am willing to wager that anyone who gives it a real shot will be impressed at the productivity gains -- which generally stem from QML's expressiveness and not having to deal with React's over-complicated design. Not to mention, you'll not waste time because some component you made behaves differently across browsers. You'll also notice a complete lack of the dogma that tends accompany modern JS frameworks and libraries.
It also feels good to know that your UI may be a bit more performant that DOM based UI's.