..., not having unsigned types, as in Java, ...
import unsigned
533 karma · joined October 29, 2012
..., not having unsigned types, as in Java, ...
import unsigned
- No curly braces around anything.
- Whitespace seems to be important, just like python.
Anyone has an example of a popular good BDFL-free project that was this way from the start?
That's what they like telling the world. They probably employ a lot of smart people, because they can afford better work conditions and salaries.
However, they don't have the monopoly on smart engineers. You can't rank people from best to worse: everyone is different. You can certainly recognize that some people are smart, but there is more smart people outside of google than inside.
The notion that they "have the best" is ridiculous, because there is no such thing as "the best engineers".
I'd prefer saying they have optimized picking their engineers so that they have more chance of picking smart ones.
The Nimrod programming language is finally featured for the db tests (at least on i7. Not sure what happened with ec2 and peak, as neither jester nor nawak seem to appears in the results).
It fares pretty well when the database is involved.
Look for the nawak micro-framework, in the top 10 both for fortunes:
http://www.techempower.com/benchmarks/#section=data-r9&hw=i7...
and updates:
http://www.techempower.com/benchmarks/#section=data-r9&hw=i7... )
And there is room to grow. That micro-framework will not be the best for the json or plaintext tests, but once the database needs to be involved, it is trivial to add more concurrency: firing up more workers (1-3meg each in RAM) acts as an effective database connection pool (1 database connection per worker).
edit: Why should you care? Nawak (https://github.com/idlewan/nawak) is a clean micro-framework:
import nawak_mongrel, strutils
get "/":
return response("Hello World!")
get "/user/@username/?":
return response("Hello $1!" % url_params.username)
run()
It's an easy rule.
Just like I prefer static strong typing...
I did notice that it was a lot worse on small font size, as the article did too, and it's really annoying: font are supposed to be scalable, why isn't there the same kerning errors on bigger sizes?
If you're satisfied with pure CSS and Javascript, the only thing you really need is a build tool for concatenation, minification and gzip. And livereload. And probably normalize.css.
-> I use uglifyjs and uglifycss
-> I use tiny-lr for livereload (https://www.npmjs.org/package/tiny-lr)
-> I use a Makefile, because it's the most simple to modify and adapt. When I have several targets of the same type (ex: build.min.js and debug.min.js), I use a yaml file with a custom python script for concatenation. See gulp.js and a thousand others for alternatives, YMMV (my Makefile nowadays: https://gist.github.com/idlewan/11012492). Magical bit for running make every time a file changes:
watch:
@inotifywait -m --exclude ".*\.swp|.*~" -e moved_to,close_write -r . | \
while read; do make -s; done
-> I use Stylus with the nib library (https://github.com/visionmedia/nib). Alternatives: LESS, SASS, and some others. You might want to add some grid and 'responsive shortcut' mixins on top.
bigger($minwidth)
query = "screen and (min-width: " + $minwidth + ")"
@media query
{block}
// usage:
.my-div
font-size 20px
+bigger(520px)
font-size 30px
-> I use Jade (https://github.com/visionmedia/jade), because it runs on the server for Python, Node.js and soon Nimrod, and on the client with precompiled templates. Alternatives: Mustache and a thousand others, YMMV.
Stylus is only about 3.5 years old. But if all development were to stop now, I'll still be able to use it 5 years down the road. It probably helps that npm dependencies are pinned to a specific version.
C has been around for dozens of years, but you can consider its feature-set pretty much frozen. That's about the same thing as being satisfied with (CSS compiler X)'s feature set and sticking with it.
DSLs like the ones for CSS compilers are feature-complete fast enough. You don't need to wait 10 years for it.
(modify Stylus line,
save).repeat(500)
(modify Stylus line,
save,
focus terminal,
run make (or whatever your build tool is),
focus browser window,
ctrl-r,
focus editor window).repeat(500)
(modify CSS line,
save,
focus browser window,
ctrl-r,
focus editor window).repeat(550)
It's so obvious that the current freedombox website is targeted at computer geeks only and not general people. It is not 'super easy to install' if it's not granny-proved.
Even if you had a turnkey solution (it doesn't exist yet) to self-host emails & stuff, the companies selling it wouldn't be able to get good search engine rankings.
The web giants have no interest in solutions that don't require them to host your data (so they can serve you advertising or hosting plans). Even small shops are usually based around a Service As A Software Substitute (SaaS) business model and don't give a crap about you not depending on them when you start their application.
You shouldn't search only for people who already know the static site generator you plan to use: any good developer that uses the CLI will have no problem using it.
When your CSS compiler takes care of all the stupid -webkit-/-moz-/... prefixes, allow you to define variables, mixins, use loops, you gain a great amount of power and your code is a lot cleaner.
When your build system integrates with livereload and make your changes appear instantly as you save, you gain speed and comfort.
That's major benefits for little to no inconvenience. I don't know about the necessity of CSS frameworks, styleguides or package managers, but some tools are just too good. It's not about the end result, it's about using better tools to get to it.
That's really cool! Thanks!
Year after year, you could upgrade the SoC and memory while keeping your case+screen+screeniopcb+batterypcb+battery.
Right now, I have no idea if I'm able to use the font for a website or for a mobile application. You may provide .woff and @font-face .css, but you don't explicitly say that redistribution through @font-face is allowed. I also have no idea if I can embed the font in a mobile application (phonegap/cordova) through @font-face.
That's what bugs me when designers provide 'for free' font files on a behance page, and what is also the case here: I am explicitly authorized to install the file locally, sometimes I am explicitly authorized to use it for 'commercial projects', and almost never am I explicitly allowed to redistribute it (which renders possible to use it on a website with @font-face or in a mobile or desktop app). As a developer, that sucks. That makes it seem like the 'free font' is for designers only (in the sense of: people that will only use the font to make an image, not a document, not a program).
These problems are of course already solved by the SIL open font license (http://scripts.sil.org/cms/scripts/page.php?item_id=OFL_web): with fonts released under this license, I am able to fix problems with the font (kerning etc...), I am able to redistribute it (@font-face, embed) AND the original designer is protected from people who want to sell the font ("The OFL allows the licensed fonts to be used, studied, modified and redistributed freely as long as they are not sold by themselves.").
If you want to sell the font, go ahead and do it! However, promoting it here as free font for a limited time to a crowd of people who have a good chance of being developers, well...
Who knows what the Oculus people are actually thinking? That's why we usually make hypothesis and conjectures: we can't prove it wrong or right, we still think something's fishy. I however agree that the tone of the article sounds too certain.
I'd prefer if bullet points were used sparingly though, you could just make use of headings and paragraphs. A very long list of points looks unstructured and is more difficult to read.
I rewrote the whole game's code as an exercice soon after it was released, and took special care in using CSS transforms and not creating/forgetting javascript objects constantly (I wish I knew if that last point made a difference in performance on mobile, but I wouln't know how to measure it). I also added a tutorial screen and an animation for a forbidden move.
That's why I can personally recommend my ad-free clone ('shameless plug' and all that), that you can find here: https://play.google.com/store/apps/details?id=com.erwan.game... or by searching "2+2=2048" in the play store/windows phone store. The swiping mechanic works great with it, so please tell me if you find any issues with it.
It felt great at first, but there was two major problems for me:
- with the laptop desk I had to slide under it each time I wanted to use the computer and grab the external keyboard, which isn't instantaneous like getting up/sitting down.
- I was waaaayyyy too sleepy lying on my bed. Had 2 minutes micro-naps all the time.
Right now I still often program in my bed, but with the screen vertical and at eyes height on the laptop desk, and my back resting against a bean-bag chair. It's much more comfortable than a standard desk-chair combination, I recommend people try it. I avoid the use of a mouse, however, and my laptop is configured to be very keyboard-friendly, so there's also that to be taken into account. Using a mouse isn't impossible, but I'm much more performant without one.
Humans are masters at adaptation. I guess we should just wait and see.
Problem not solved: the population still has problems being fed the right things for their health to improve.