lhecker

I guess the author must have been pretty happy when Swift came out, with all of it's glorious Unicode support...

Which is, btw, really surprising because the US had a avg. speed of 6.0 in 2013 and 11.5 in 2014, while Germany only improved from 7.7 to 8.7.

IMHO that's really strange...

Did something major happen between 2013 and 2014? Because otherwise I can't think of any reason that would double the average speed of a whole country with a population of over 300 million.

So your opinion is "If it's slow it's okay, because it's safer than optimizing?".

I'm sorry but I have to disagree completely...

I'm currently rewriting the node-postgres module from scratch and my implementation is between 3 and >1000 times faster than the original (this is not even a joke). And you know why? Because the original actually contains those hacks you're talking about and not the other way around.

And that's where your actual noticable inefficiencies far too often stem from: Inexperienced developers who don't know how to do it the easy way - inefficiencies due to huge workarounds that have hidden costs.

E.g.: Not using builtin methods but writing buggy workarounds. Or even very basic stuff like: Using expensive functions within loops instead of hoisting those outside of it.

I wouldn't even call those "optimizations".

Yikes... That's even worse.

Well at least Microsoft stopped doing that and are now displaying a message that the password is too long instead of doing it silently.

Yep exactly that. It would be great if I could just use some whole words as the password for accounts which I need to use often or are really important and thus IMHO make password stores impractical (e.g. desktop login, Gmail, …)

I completely agree with the author, but... what he completely misses is the biggest annoyance: maximum length rules.

I'd probably sacrifice my firstborn if Microsoft would finally wake up and accept passwords longer than 16 goddamn characters...

In your blind love for Rust you seem to forget that it in fact operates with pointers - everywhere.

The thing is that Rust either tracks the lifetime of a naked pointer (similiar to std::unique_ptr), or you wrap pointers in objects which facilitate reference counting to track the lifetime (similiar to std::shared_ptr).

In the end both kinds operate on generic, unsafe raw pointers - safe only thanks to ownership tracking and "boxing".

The only difference here is that Rust thankfully made it opt-out while C++ unfortunately needs to use opt-in.

But yeah... I'm eager to hear your explaination how Rust doesn't use those stupid pointers. Maybe you can create a new computer architecture too? I mean since x86 uses pointers and stuff. Maybe we should use garbage collected languages for that, huh?

I fiddled around with the code and I think I found the reason for the lags:

The "stylesheets/styles.css" file contains the following rule at the beginning:

  body {
    ...
    background: url('data:image/png;base64,...') fixed;
  }

If you remove the "fixed" attribute it's... fixed! (Oh, the irony...)

I would be careful with the word "always", because that's a pretty long time span compared to since when "programmers" even exist...

Thanks!

Let's see if I get it compiled and can test it right now without waiting for the offical release. :> Wohooo~ Open-Source!

If I could I would upvote this twice.

So yeah: IMO a browser really should be just the browser with a good Addon-On API. That's why I would add a third point to your list:

- The Browser Team should provide (optional) Core-Plugins which are easy to install and in turn provide basic but useful features. For instance those mentioned in other comments here (e.g. uBlock, MAFF-Support, Mouse-Gestures, ...)

Uhm... Using "-1" to assign the maximum value is in fact as standard and cross-platform as using std::numeric_limits, which was basically my entire point.

The difference between those is only "textual solution" VS "mathematical solution" and thus a matter of personal preference.

Just a nitpick: Assigning a negative value to an unsigned integer is perfectly safe and well defined (i.e. integer overflow for unsigned integers is well defined in the C++ spec).

Using -1 for size_t is sometimes even prefered to assign it's maximum value, since there is no cross-platform #define for it (most use either SIZE_T_MAX or SIZE_MAX).

In fact llvm's libc++ uses it for it's std::numeric_limits implementation and for std::string's npos.

FYI: This is utter nonsense and just shows how poorly the journalist did his job:

http://imgur.com/a/zN8Kv

(I do think it's funny though if guys/websites like these do their little propaganda, which later on turns out to be complete BS.)

Does anybody else experience issues with Truecrypt 7.1a?

It displays

  X:\ is not accessible.
  Incorrect function.

and the Computer Manager displays the drive with the RAW type.

- Even though the filesystem is intact (tested on another Windows 8.1 computer) and

- chkdsk showing NO errors (yes that's right: it even shows the filesystem as being NTFS).

Aside from that my UI/UX experience with Windows 10 is great and I'm really happy. The above thing is a bummer though.

For a full and complete example take a look at one of my most recent projects :) https://github.com/lhecker/se2-bga

I'm currently studying computer science in germany. In a team of 5 we created the above project for a software engineering assignment. But in the end I wrote the entire code part alone. :D

It implements a simulated elevator and displays the internal state in a UML state machine diagram.

It features:

  - Grunt build system
  - JSX + ES6 to ES5 transpiler using babelify and browserify
  - LESS to CSS transpiler
  - karma + jasmine test system
  - live reloading ("grunt serve")
  - building a static page from the source code ("grunt dist")
  - building a nw.js based app from the static page ("grunt build")

The magnet link didn't work for me. But then I tried using http://infotomb.com/eyyxo.torrent instead, which worked immediately with Transmission 2.90 (OSX) and Tixati (Windows).

btw:

The MD5 of eyyxo.torrent is 26183ae8f24e798a15d77dd3476f5ed9

I mirrored the torrent file on my server in case infotomb gets offline again: https://hecker.io/eyyxo.torrent