1,123 karma · joined February 12, 2020
That is wrong. It makes a huge difference for the overwhelming majority of users.
In addition, you are trying to extrapolate the design choices of
+ an extremely specialized UI,
+ for trained experts,
+ intended to never break,
+ designed decades ago,
+ to be used while in combat,
+ etc.
...just to support your preferences and beliefs in UI design.You may be right or not, but comparing web pages with cockpits does not make any sense at all.
It is like saying a touchscreen is thousands of switches just because it has that many sensor points.
The reality is that making good games is extremely hard, and has always been.
Unity is not the first game framework, there have been many along the years. Flash being one of them (while not even designed for that originally!).
Some of them are easier, some are more featureful, some have better graphics, some are specialized into a genre etc.
While some genres need almost no code, others are full of pages of tricky game logic. And that is without counting into account the engine code.
Further, Unity had nothing to do with Steam being flooded. The actual reason is that
1- Valve pivoted into being a distribution platform,
2- they stopped curating what goes in,
3- gaming exploded and became way more mainstream (along with streaming, e-sports and programming, all which helped a lot), and
4- people started making money selling courses, degrees and content on how to make games.> have no comparable analogue in traditional text-focused, non-IDE editors.
The same features have been there in TUI editors for many, many years. There is nothing visual about the backend that handles those queries.
Whether the interface is easier to use or not is a different matter, but the features have been there for decades.
> Not to mention visual debuggers
Well, yes, visual debuggers are better with a GUI, that is obvious.
> not to mention remote debugging!
Remote debugging is very common. What you are thinking of is visual ones.
> However, objective tests show that even highly skilled users aren't as fast at completing high-level tasks as mouse-users.
Citation needed.
Blender, for instance, is praised by artists for its hard modeling productivity thanks to all the shortcuts.
A few years ago when I worked in VS, I used all kinds of shortcuts. It does not matter that the tool has a GUI or not to make the keyboard useful. It is orthogonal.
> took days or weeks to solve the same problem! Days!
That is just nonsense. There is no way one takes days/weeks to "debug" something that takes 30 minutes in another general purpose language.
Either the task could be trivially solved using the .NET standard library and not the others (which makes it incomparable), or they picked up participants with no clue in the other languages.
The debugger or the GUI/TUI distinctions have nothing to do with that. A visual debugger is most useful when dealing with very big code bases that you did not write yourself. For a programming puzzle that fits in 100 lines, a visual debugger is irrelevant unless you are new to programming.
Not certain Intel processors: all of them. The CPU will reduce its clocks, reducing its overall performance.
Using AVX256 or AVX512 is easily a net negative on performance, depending on the software, input data and other processes running in the system.
Unless you are certain you have enough data to offset the downclock, don't use them.
The person you replied to said:
> There is no proof that these outperform traditional CPUs at all.
To which you replied talking about embedded market share and supercomputer which have nothing to do with that.
Since now you mention Apple and MacBooks, which haven't been even mentioned, I think you are answering to the wrong thread/post.
Two threads reading and writing to the same memory area do not necessarily give problems. In fact, many software is built to exploit several facts about how memory accesses work with respect each other.
ARM processors give very few guarantees, so code has to workaround that.
As for supercomputers, >90% of them are Intel/AMD.
The other extensions do not trigger it, not even AVX256.
With AVX512 is not always a win, and you don't even know until you try in particular hardware.
Messing with the type system is using it for things you really should not in any reasonable project. For instance, some of the Boost libs with their overgeneralizations that 99% of users do not need.
Like when telephone lines were introduced, they were a massive boost to productivity. Even if they could be used as a social feature within companies, it was not why they were useful there.
Recompiling fast helps the most when learning to program, but not for actual applications with some complexity.
Many applications do not even have meaningful output by just running it, for instance they may take a long time to compute something meaningful.
When I am working, I am not trying to be social but to be professional.
Then they started to grow, specially GitLab in the beginning, and now try to be a single centralized solution for all software development needs like Atlassian, IBM and others had always been selling.
I have never cared about all the "social features" that work tools seem to always end up introducing...
Rust is slower overall, which is why people tend to complain. And if you start messing around like in C++, then you get even crazier times.
But in neither case it is a dealbreaker compared to other languages. Go proponents claim compilation speed is everything, which is suspicious. I do not need to run my code immediately if I am programming in C++ or Rust. And if I am really doing something that requires interactivity, I should be doing it another way, not recompiling every time...
Like Walmart or Amazon, the problem is for devs, not customers.
Yes? I haven't claimed there aren't free native apps.
> Web apps tied to subscriptions are also plentiful.
Fair, but most of the ones I know are usually technical apps or they offer something else that is not about software (for instance, storage more than the app).
> the web is unique in allowing you to actually inspect the source that is running on your machine
That is not unique, nor true.
Uniqueness: you have apps made in scripting languages everywhere. Even for compiled languages it is a decision not to give you the code, not a technical one.
Truthness: many webs are obfuscated on purpose like native apps are.
> you have no way of verifying that the code in an open source repo is what actually runs inside your iOS app.
False, you can definitely verify that a binary matches the source code in deterministic builds and even provide debugging symbols etc. The fact that many projects don't care about that does not mean there is "no way", it just means the overwhelming majority of users do not care.
And that is assuming they are trying to "protect you", but that is a different discussion.