1,366 karma · joined April 2, 2010
It can be found in the cover art of "10000 Days", an album from American metal band Tool. The original box comes with two magnifying lenses like this:
http://s21.photobucket.com/user/Stonergrunge/media/Mis%20cos...
This (and others in the cover) look stunning through these lenses.
E.g. I have a very innocent 2000-line MainWindow.cpp that weighs 244419 lines when measured with gcc -E -o - | wc -l
And I doubt it was trained. It seems to be following a predefined procedure instead of learning by itself.
It seems to have come a pretty long way if you ask me!
But how do I know the battery reports honest numbers? If all these years spent dealing with hard disks tought me anything, it's that what's being reported by the device could be totally different from the reality :)
Perhaps some brands charge a premium for a "long lasting" battery whose only actual difference from a regular one is a firmware hack that keeps it at %80 charge? Can I actually know this?
Example for a popular home to work commute: http://cycleroute.org/?slat=41.061029&slng=29.00681199999996...
That's more a job for SNMP clients anyway. Actually, just look at Nagios/Icinga :) It's a very mature and well-rooted infrastructure monitoring solution.
I'm looking at Dell's machine and yes it's got a higher resolution display (but is it better at that display size? I hope!), and presumably an updated processor, but that's it. No nic, no disk spinner, less ports, no VGA, etc. Call me old-fashioned but I can't consider a laptop without a couple easy ways to get data on/off (e.g. ethernet ports, disk spinners) as a development workstation.
Top that and I'll pay you.
And shame on you, Sony, for not being able to properly sell today's market leader that you came up with two years ago. Shame on you.
You and I must have very different perceptions about the way a server is "having a bad time" :)
I was assuming they were at various stages of processing an incoming request, which means they were blocked on either legitimate disk i/o or swapping. It's very difficult to log in even locally in that case, because the login process can't read /etc/passwd in time.
> Also I'm not sure why you think that the kernel thread scheduler is all that good, or why it shouldn't be considered "outside our control.
I was just trying to say that it's dangerous to give non-trusted peers big influence on the way the scheduler behaves.
Ever tried to ssh into a one-thread-per-connection setup under heavy load? Assuming you managed to log in, it'll be very very difficult to get htop to execute when it's competing with 2k other processes for cpu time.
So, spawning a thread for every incoming connection request is a bad idea. But what about spawning a thread for every outgoing database connection?
The memory overhead of a thread compared to a tcp socket may be significant, but it's nothing compared to a database connection and all the other resources tied up serve that one database query. And best of all, you can refuse to setup a database connection without upsetting your user and e.g. serve from cache instead, but you can't refuse an incoming connection request.
According to the Postgres guys [1]: "A formula which has held up pretty well across a lot of benchmarks for years is that for optimal throughput the number of active connections should be somewhere near ((core_count * 2) + effective_spindle_count)"
Assuming you got two tablespaces on two raid 1 arrays on a 16 core machine, that's 16 * 2 + 2 = 34 threads plus the event loop thread, maximum.
According to those numbers, there doesn't seem to be much stopping you from running your data access logic within a thread.
[1]: https://wiki.postgresql.org/wiki/Number_Of_Database_Connecti...
1) I can't say I find migrating blocking code to non-blocking code trivial. The bad thing about it is that you never know what you left behind. Blocking code doesn't tell you when it's blocking your event loop.
2) Async helps apps use less memory by doing away with thread overhead in connections, but is otherwise suboptimal (hinders latency) under higher cpu load scenarios. It never was a way of getting additional "free performance" for your app.
You can actually use Spyne with Django as well[3] (and Spyne has a "general model serializer" that can be used with a lot less boilerplate than what's shown here).
Spyne supports a lot of protocols as well as persisting to a relational database via SQLAlchemy.
Disclaimer: I'm the author of spyne.
[1]: http://spyne.io
[2]: https://pypi.python.org/pypi/Flask-Spyne
[3]: https://github.com/arskom/spyne/tree/master/examples/django/...
http://hackersurfing.com/assets/dinner5_s.jpg
if you're trying to make an impression, that's the impression you're going to make. sheesh.
See the relevant bit from Qt's documentation for more information: http://qt-project.org/doc/qt-5/why-moc.html
https://docs.python.org/2/library/inspect.html#inspect.isgen...
I love the battery life. Perhaps thanks to using Qt/C++ instead of a higher level language/framework, or perhaps thanks to me being social-medially-challenged, the standard 2200 mah battery takes me for a good chunk of 48 hours.
Yes, there aren't much apps for it, (there was a time when you could practically download the entire Jolla store to your phone) but almost all of the apps are open source. If you're craving for the latest episode of Brain Crush Saga, you're not in the target audience anyway.
There are also a couple of factors which make it a unique offering:
-It's not from Google, it's not from Apple, so I'm a bit more comfortable privacy-wise.
-The concept of "The Other Half". It's sort of a "hardware app" that you can use as the back cover of your phone. For example, there's a kickstarter for a The Other Half Keyboard running right now: https://www.kickstarter.com/projects/2028347278/tohkbd-the-o....
-No front-facing buttons! Huge success design-wise. Not gorgeous like the N9 (reportedly due to some patent issues), but still very eye-pleasing.
All in all, very cute device, but definitely not (yet) for everyone.
As for the tablet, I expect to be a lot more productive with it compared to the toys on the market now, especially thanks to it being an Intel-based device with a proper Linux distribution. And at ~200$ for this kind of device, to me it's a bargain.
The Indie GoGo page is buried far down the page, so here it is for your convenience: https://www.indiegogo.com/projects/jolla-tablet-world-s-firs...
Keep up the amazing work, Jolla team, you are making a difference.
Disclaimer: No affiliation, just a happy customer.
So, Microsoft is finally adapting. But what are they actually doing? Why did Microsoft finally decided to make .Net cross-platform? What's in it for them?
Look at what's in this shiny new package: They've open-sourced just the core runtime. They are not open-sourcing Visual Studio. Or WPF. Or SQL Server. Or Active Directory. Or Office.
There's one thing the Linux ecosystem is pretty good at: Scaling, both up and down. There are technical reasons for that, but none could possibly be an issue for a software powerhouse the size of Microsoft. There are also commercial reasons for that, most important being: You just can't beat free.
So that's what Microsoft is finally moving against -- Dear startup founder who is afraid that licensing costs will eat him/her alive while his/her "Growth Hacking" strategy is working, dear embedded programmer whose tiny IoT device that just can't cope with the whole Windows mumbo-jumbo, welcome to the Microsoft platform -- You can now safely run your C# on these free platforms as well.
So, Microsoft is finally back in the game. They even seem to be playing nice. But the question in everyone's mind is: For how long?