If you really used GTK+, Qt, wxWidgets, WinForms in C#, etc, I'm sure you'll be familiar with GUI hierarchy, as all of those you've cited are based on inheritance hierarchy, and if you've used them seriously, you probably created re-usable components inheriting any other component. And, funny, any reactJS component is inheriting a reactJS component too. It's just so bad designed that it supports just 1 level of inheritance.
I joined a reactjs/flux project some months ago. I properly learned how it works quickly, and liked the idea. Several years ago I've worked with desktop UI apps (in C++, later Java/Swing and C#), so I had no trouble with the idea.
But then I tried to create, like in the GUI desktop world, when you have a nice hierarchy of components/containers, a parent component that will have most the logic, then 2 children classes, including only the different logic. First wall: the same guides in other crap OO language/frameworks. "you're not supposed to use inheritance, you need to use composition ".
The most irritant issue: of course, several things that worked in the past with reactJS simple were removed or are under constant changes. I can even handle that, but the problem: a LOT of the erros and warnings just don't handle a stack. They simply give you a warning/error message and you'll have to dig in the code where it was raised. Again, terrible OO.
Even flux it a weird flow, because it relies in a dumb event system: just a big pipe raising all events. If you want to listen for an event, you need to plug into this big pipe, listen all events and use a switch/case to get the ones your component wants.
Not to mention some repeat-code-everywhere approach, when you have thousands contants that are just the same string as the constant. This for a dynamic language... i.e., people will make a typo in the name of the constant too and nobody will notice.
I can just saw that JS turned the new PHP: developers that don't want to proper learn how to code everywhere with "brilliant ideas".
See this article... they mention that Alphonso hear only "TV adds", but of course it's hard to a software distinguish between talking and TV adds: https://www.nytimes.com/2017/1...
The reason why USA planned a moon travel was not because "it's hard", it was because Russia sent a man to the space first. After the competition is over, all stopped. Maybe China sending man to the space/moon/Mars will make USA react again. Need or competition is the fuel for mankind.
They call "Material", but it's the same unicolor as other companies. I.e, icons with no meaning (triangle for back, square for home... or circle for home?), no color, no underline to indicate clickable text (nor buttons), no border or shadow to help you to identify a window, no text to help and lack of shortcuts for the advanced users, extensive use of light text color in white background, no way to customize a thing. Appears that the cool in modern design is just ignore every HCI rule that was build in the last 40 years.
Interesting that they are discussing the possibility of something like a backdoor on it. Just wondering how the rest of the world should behave when we have several US-made softwares that were already proved to contain NSA backdoors.
Hm, right, thanks for sharing this info. Indeed, my bad to assume every country will be the same regarding this. To answer your question: yes, it's different here. The gas station are always big (it's a lucrative business), and the customer (driver) don't handle the gas pump. There are always 2 or 3 employees to handle it for you. And it's almost mandatory they're friendly (as they'll try to sell you additional services). So, last time I gone to a unknown place with no GPS signal, I just asked directions at the gas station.
To be honest, I got a Moto G (I think it's the 4th generation) for my wife and it was surprisingly lean. Not even a "standard" photo viewer program (it has Google Photos). Very fast. No single one crapware.
In the time Slack has not a Linux client, I've created a similar client using qtwebkit for Linux: https://github.com/raelgc/scud.... It was a bit popular, then Slack released the official client, and I thought that my simple client was dead. For my surprise, it's still alive for all people complaining about resources.
Sure, still a web container running the web version with desktop integration, but at least is using directly a web engine, not an entire browser. The reason is because Slack has no messaging API at all.
Two downsides: Slack keep changing their JS all the time, so it's a cat and mouse game. And qtwebkit itself keep breaking small stuff, so, last month I got 2 major issues: Arch Linux got the newest qtwebkit version, and it was crashing with a dump, not even a python stack (fix was downgrade. Ubuntu 16.04 faced the opposite: Slack upgraded their CSS and qwebkit version included in Ubuntu 16.04 was no more properly rendering the CSS (I pointed people to a package that upgraded 16.04 webkit.
I contacted Slack at least 2 times offering helping on Linux as a volunteer, as their client is just a "compiled" JS and I told them I can: fix some issues, help testing and improve integration with major Linux desktops, but most of the times I have no answer or the traditional "we appreciate, but no".
I totally agree. If you're casual user, you'll face the same browsers (well, not IE or Edge), etc. If you're a developer, the world will be a way better for you (better support for Java, Ruby, PHP, Python, multiple language interpreters setup, like several JMVs, RVM, etc, out of box, all installable from few clicks or bash commands). The only downside in current days is gaming (Windows support is better). But I use this as an advantage for me: no gaming in my working computer:)
I used Nokia smartphones several years before iPhone, with a real browser and running other desktop similar tasks (watching videos, listening mp3, playing really cool games).
The marketplace idea existed before in Debian based distros (mainly Ubuntu with a proper catalog software, but not nicely implemented as Apple one).
Kill flash: yes, but the reason why they've made it was because Flash is terrible with touch, and with Flash in browser, basically you'd have access to many games that they expect to see in the store. Anyway, a nice achievement!
One missing achievement was to properly implement a touch device. Before it, only resistive single-point touch screens with bad response.
Wondering if the site was built by people learning in the project classes. It ask me my language every new page load, the previously chosen language is not selected, and sometimes, after select the language, it redirects to a 404 page.
Slashdot Mirror
If you really used GTK+, Qt, wxWidgets, WinForms in C#, etc, I'm sure you'll be familiar with GUI hierarchy, as all of those you've cited are based on inheritance hierarchy, and if you've used them seriously, you probably created re-usable components inheriting any other component. And, funny, any reactJS component is inheriting a reactJS component too. It's just so bad designed that it supports just 1 level of inheritance.
I joined a reactjs/flux project some months ago. I properly learned how it works quickly, and liked the idea. Several years ago I've worked with desktop UI apps (in C++, later Java/Swing and C#), so I had no trouble with the idea.
But then I tried to create, like in the GUI desktop world, when you have a nice hierarchy of components/containers, a parent component that will have most the logic, then 2 children classes, including only the different logic. First wall: the same guides in other crap OO language/frameworks. "you're not supposed to use inheritance, you need to use composition ".
The most irritant issue: of course, several things that worked in the past with reactJS simple were removed or are under constant changes. I can even handle that, but the problem: a LOT of the erros and warnings just don't handle a stack. They simply give you a warning/error message and you'll have to dig in the code where it was raised. Again, terrible OO.
Even flux it a weird flow, because it relies in a dumb event system: just a big pipe raising all events. If you want to listen for an event, you need to plug into this big pipe, listen all events and use a switch/case to get the ones your component wants.
Not to mention some repeat-code-everywhere approach, when you have thousands contants that are just the same string as the constant. This for a dynamic language... i.e., people will make a typo in the name of the constant too and nobody will notice.
I can just saw that JS turned the new PHP: developers that don't want to proper learn how to code everywhere with "brilliant ideas".
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety". Benjamin Franklin.
See this article... they mention that Alphonso hear only "TV adds", but of course it's hard to a software distinguish between talking and TV adds: https://www.nytimes.com/2017/1...
It's exactly this way here in Brazil (which uses the metric system): McDonald's say that Quarter is a 100gr. patty.
The reason why USA planned a moon travel was not because "it's hard", it was because Russia sent a man to the space first. After the competition is over, all stopped. Maybe China sending man to the space/moon/Mars will make USA react again. Need or competition is the fuel for mankind.
You mean... Unciclopedia http://en.uncyclopedia.co/wiki... ?
Well, if they repeat the same for network speeds, maybe in 10 years we can run Lotus Notes in an usable way.
Sounds like you never used Unity. Unity is not touch centric. Indeed, is the best DE for a keyboard user. No related to Gnome 3 touch UI at all.
... and first than MS, but I think they're not paying media like TheVerge to share this.
They call "Material", but it's the same unicolor as other companies. I.e, icons with no meaning (triangle for back, square for home... or circle for home?), no color, no underline to indicate clickable text (nor buttons), no border or shadow to help you to identify a window, no text to help and lack of shortcuts for the advanced users, extensive use of light text color in white background, no way to customize a thing. Appears that the cool in modern design is just ignore every HCI rule that was build in the last 40 years.
Interesting that they are discussing the possibility of something like a backdoor on it. Just wondering how the rest of the world should behave when we have several US-made softwares that were already proved to contain NSA backdoors.
Hm, right, thanks for sharing this info. Indeed, my bad to assume every country will be the same regarding this. To answer your question: yes, it's different here. The gas station are always big (it's a lucrative business), and the customer (driver) don't handle the gas pump. There are always 2 or 3 employees to handle it for you. And it's almost mandatory they're friendly (as they'll try to sell you additional services). So, last time I gone to a unknown place with no GPS signal, I just asked directions at the gas station.
Exactly! Gas stations are perfect for this. Sorry, English is not my native language :(
He is missing an important tool: while in a gas station, ask about how to reach the destination, or at least, the next POI.
To be honest, I got a Moto G (I think it's the 4th generation) for my wife and it was surprisingly lean. Not even a "standard" photo viewer program (it has Google Photos). Very fast. No single one crapware.
The good: Git is decentralized, so everybody can continue working. The bad: several companies are using it as origin.
It's just another Electron app running the web version. In this sense (what is discussed here) is exactly the same as Slack App.
Feel free to create a PR with the changes you need or join as a contributor!
In the time Slack has not a Linux client, I've created a similar client using qtwebkit for Linux: https://github.com/raelgc/scud.... It was a bit popular, then Slack released the official client, and I thought that my simple client was dead. For my surprise, it's still alive for all people complaining about resources.
Sure, still a web container running the web version with desktop integration, but at least is using directly a web engine, not an entire browser. The reason is because Slack has no messaging API at all.
Two downsides: Slack keep changing their JS all the time, so it's a cat and mouse game. And qtwebkit itself keep breaking small stuff, so, last month I got 2 major issues: Arch Linux got the newest qtwebkit version, and it was crashing with a dump, not even a python stack (fix was downgrade. Ubuntu 16.04 faced the opposite: Slack upgraded their CSS and qwebkit version included in Ubuntu 16.04 was no more properly rendering the CSS (I pointed people to a package that upgraded 16.04 webkit.
I contacted Slack at least 2 times offering helping on Linux as a volunteer, as their client is just a "compiled" JS and I told them I can: fix some issues, help testing and improve integration with major Linux desktops, but most of the times I have no answer or the traditional "we appreciate, but no".
I totally agree. If you're casual user, you'll face the same browsers (well, not IE or Edge), etc. If you're a developer, the world will be a way better for you (better support for Java, Ruby, PHP, Python, multiple language interpreters setup, like several JMVs, RVM, etc, out of box, all installable from few clicks or bash commands). The only downside in current days is gaming (Windows support is better). But I use this as an advantage for me: no gaming in my working computer :)
I used Nokia smartphones several years before iPhone, with a real browser and running other desktop similar tasks (watching videos, listening mp3, playing really cool games).
The marketplace idea existed before in Debian based distros (mainly Ubuntu with a proper catalog software, but not nicely implemented as Apple one).
Kill flash: yes, but the reason why they've made it was because Flash is terrible with touch, and with Flash in browser, basically you'd have access to many games that they expect to see in the store. Anyway, a nice achievement!
One missing achievement was to properly implement a touch device. Before it, only resistive single-point touch screens with bad response.
Man, no need of strike back. He is just asking about the unique number of users. Even you're mentioning that 1, 2, 3, 4 and variations are obsolete.
Wondering if the site was built by people learning in the project classes. It ask me my language every new page load, the previously chosen language is not selected, and sometimes, after select the language, it redirects to a 404 page.
The problem always is: if there is a backdoor, the manufacturer is not the only one able to explore it.