I don't understand this trend for less and less keys. I get that it can be nice to have more room on the desktop but why would you give up the arrow- and F-keys. They are so useful and the space benefit without them is marginal.
1,011 karma · joined March 31, 2017
I don't understand this trend for less and less keys. I get that it can be nice to have more room on the desktop but why would you give up the arrow- and F-keys. They are so useful and the space benefit without them is marginal.
But we'll see how well that works... I just fed the first 4 google results for "ip address converter" with 10.1: Three converters gave an error message and one came up with 0.0.0.10.
This is just sad. There was a time when I was happy to read about a new FF version for the desktop. Now I'm just waiting that they will ruin it like they did with the mobile version.
LOL, "lucky enterprise" my ass. The only poor souls who still work with that shitty bug ridden stone-age IDE from Embarcadero have to do that because they never managed to get rid of VCL (which might have been nice 20 years ago. Today it's just bad compared to modern frameworks).
Stay away from Embarcadero, don't become dependent on such vendor lock-in.
I'm pretty sure this memory extension doesn't affect uniqueness of pointers... that would indeed break a lot of software ;-)
It's quite concerning that websites are able to do this. While it is the browsers fault to support all that javascript crap I think this is also a bug in Android.
Because of the reported bug in this example (which I also encountered quite often):
- user hits ESCAPE
- my window gets key-down/ESCAPE and closes itself
- your window (which happens to be the next in the focus-order) gets key-up/ESCAPE and closes itself
> I also like being able to hold the key down to cue up a command and then at the right time, pull my hand away to execute crisply
Ok, but if your window wants to support this behavior (which is not very common) you have to watch for key-up AND key-down like the bug-report suggests.
- In the previous version when you search something in the URL bar you could long tap the search suggestions to insert them into the URL bar for editing. Gone.
- To open a new tab you have to open the tab selection with the icon on the top (or bottom) of the screen and then tap the "+"-icon in the middle of the screen. In the previous version you could just double tap the icon.
- No way to create a new search shortcut from a search box on a website. You have to manually enter a URL containing a %s. No way to search with POST forms.
- They removed the option to hide the microphone icon in the URL bar
Maybe if you have a large phone or short fingers but beside this bottom bar there are only disadvantages in the new UI, like no bookmarks in the new-tab-page. Or the additional movements/tapping you have to make to open a new tab. It's like the designers never even used the previous FF.
> and the browser is much faster
Maybe if you mainly visit shitty javascript-bloat-sites like twitter or reddit but for me there isn't much difference in loading times. The small initial pageload-speedup is lost by the time I need to scroll over all the new advertisements I previously never had to deal with thanks to uMatrix.
> but it lost some features
not just "some features". It lost _everything_ that made it better than chrome. Now there is just no reason for mobile FF to exist anymore.
> A small but vocal number of users complained
How did you measure that? I see mostly complaints and a few people who are happy because of the bottom URL bar.
Now I have my most visited sites in the new "top sites" section and the rest goes to bookmarks. Works for me but there is also absolutely no benefit to before (bookmarks are even less accessible). And you still can't reorder any bookmarks/top-sites/collections nor export/import them.
But why fix old bugs or implement requested features when you can just start completely new and ignore the users. That's definitely more fun for the programmers.
I don't get it. Firefox mobile was how old? Two years? Is that the new standard of software-development where you ditch your source every few years and rewrite from scratch?
I'm very disappointed.
How would code-signing be any better than HTTPS-certificates? That sounds like just another instance you would have to pay fees to.
how is that?
yes, but so far (C/C++2003) I always thought that something like mutex.lock() in the example, before accessing x, would be recognized as a memory barrier by the optimizer so it should be safe to access x as long as your thread acquired the lock.
Now for C++11 I'm not so sure anymore because of this last paragraph of the article:
> What’s more, since C++11 has well defined memory semantics, compiler writers are no longer forced to be conservative with their optimizations. If the programmer doesn’t specifically mark shared variables as atomic, the compiler is free to optimize code as if it were single-threaded.
Does this really mean that the above x must always be declared volatile even though it's surrounded by a mutex-lock? If so I hope there's a compiler flag do get the old behavior...
That's terribly annoying to me as a consumer so please don't do it.
I prefer to educate people to only enter credentials when they opened the website manually by themselves. That is also easier than trying to teach someone who can't distinguish between the address bar and the google-search field, what a domain and TLS is.
How does the user know its legit?
"feeling of a dystopian future"? That sounds straight like from an episode of Black Mirror.
I don't care because I don't use Apple but I still feel very offended as a human being.
WTF? How can they give such a disrespectful fuck-you response?
So does the web browser and almost every other application you install on your desktop.
> It's scary giving extensions this much access
No, it's scary giving random websites so much power like it's currently done with JavaScript. The ad blocker makes it a little bit less scary.
It is sad that todays websites offload so much work to the client. I wish they would just deliver some text and pictures (which would probably worked out perfectly fine in this example!) so that in case of bugs their server crashes instead of my web-browser.
It's an old long SVN repository with a lot of files. I would like to split it in two SVN repos but that would destroy their history. Any ideas?
> I'd expect everything to be slow.
It's actually very OK with git in cygwin-bash.