pawadu

45 ms·

1. 481.▲
   by pawadu 10y ago

   but then again, how is that different from android of today?
2. 482.▲
   by pawadu 10y ago

   Don't forget mg. It seems to be more used than uemacs these days, possibly thanks to the openbsd project: [1]: https://en.wikipedia.org/wiki/Mg_(editor)
3. 483.▲
   by pawadu 10y ago

   > less hassle to work 24/7 what does that mean?
4. 484.▲
   by pawadu 10y ago

   In theory, maybe. But have you seen the corresponding code in the linux kernel when they try to probe a partially known component and at the same time go around all kinds of bugs and errors and differences in silicon revisions? All those ma
5. 485.▲
   by pawadu 10y ago

   +1 for the mi band! I think for me the version with the small display is the perfect smart watch: http://www.mi.com/en/miband2/ It has basically all I need (30+ days battery life, display time, step and distance
6. 486.▲
   by pawadu 10y ago

   > Device trees are needed because manufacturers did not create self describing hardware. This is impossible to do beyond trivial components. Most devices are complex systems of interacting components. Also, do you want the same lazy manu
7. 487.▲
   by pawadu 10y ago

   To be fair, the new 64-bit ARMs are becoming "more RISC-y" and have the same problems as MIPS.
8. 488.▲
   by pawadu 10y ago

   or we could continue using device trees, which are much more expressive and were actually designed for this purpose.
9. 489.▲
   by pawadu 10y ago

   Sign me up too! But to be honest, the problem with Android is not the Linux kernel but the fact that most phones were never designed to be continuously updated.
10. 490.▲
    by pawadu 10y ago

    Because you have to move fast and break things and it is very hard to break OpenBSD :)
11. 491.▲
    by pawadu 10y ago

    Thanks for the answers! > Other than that, I'm not totally clear on the "standard library being too large" IIRC their Rust kernel hit some size barrier (for the bootloader?). The author tried to build a smaller standard li
12. 492.▲
    by pawadu 10y ago

    So I can cause some serious economic damage around the Bay area by spoofing a few NTP messages?
13. 493.▲
    by pawadu 10y ago

    Was about to write the same thing! I have paid significantly more than $3 for something that turned out to be garbage (side note: Humble Bundle team, you gave charity a bad name). Haven't encountered anything similar while buying chees
14. 494.▲
    by pawadu 10y ago

    I think this is unnecessary when you got <stdint.h>: typedef unsigned long int u64; typedef unsigned int u32; ... if you define your own types like this you may need to revise them when you switch architecture
15. 495.▲
    by pawadu 10y ago

    > He claims that your code will be easy to port but then goes straight to Linux system calls. Well, it is hard to see an alternative to that outside supplying your own OS with the library...
16. 496.▲
    by pawadu 10y ago

    The second half of the paper is mostly about challenges in using Rust. Some were related to the way the language handles data (i.e. challenges of sharing data among threads without using unsafe code), but there was also some that are relate
17. 497.▲
    by pawadu 10y ago

    Never heard of this app, yet... > Something else Neistat authentically shared onstage was Beme’s raise and burn rate — $6.6 million in funding, with a burn rate of $180,000 per month guess I am in the wrong business...
18. 498.▲
    by pawadu 10y ago

    Believe me, they tried. There was a minor riot among developers and many decided to stay out of the App Store (not for any ideals mind you, but because of limitations of the store sandbox)
19. 499.▲
    by pawadu 10y ago

    Fair enough, but it didn't used to be like that: https://scialex.github.io/reenix.pdf
20. 500.▲
    by pawadu 10y ago

    Well, there are two types of people in this world 1. the type that do something 2. the type that claim they could do it better than the first group (this is by no means limited to programming, it is for example pretty common in politics) So
21. 501.▲
    by pawadu 10y ago

    hah! fixed that for you. Who would complain about something as wonderful as C11, outside it not being available for your compiler?
22. 502.▲
    by pawadu 10y ago

    C does not in anyway forbid having two definitions on the same line hence char var2, *var1; is valid C while in Java this would be illegal char var2, [] var1; So the syntax is correct and all you are doing is to add style
23. 503.▲
    by pawadu 10y ago

    And yet, the OS and the browser you used to type this comment was written in C or a C-derivative like C++.
24. 504.▲
    by pawadu 10y ago

    The author has also been involved in development of "musl", a modern C11 compliant standard library implementation: http://www.musl-libc.org https://gustedt.wordpress.com/2014/10/14/musl-
25. 505.▲
    by pawadu 10y ago

    Or unix in general. I learned C by implementing my own versions of popular unix commands, starting with echo then cat and so on...
26. 506.▲
    by pawadu 10y ago

    Also, Rusts standard library is simply too big for many embedded systems. Last time I checked the compiler didn't support bare-metal and resource constrained builds without using crazy hacks. Although the situation may have improved si
27. 507.▲
    by pawadu 10y ago

    Any idea if it will be available as a physical book?
28. 508.▲
    by pawadu 10y ago

    > We bind type modifiers and qualifiers to the left. Good idea in theory but your example shows how bad it behaves in practice.
29. 509.▲
    by pawadu 10y ago

    Thanks to bitcoin, these hacks now cost companies real money. Money is something people can easily grasp, in contrast to something as vague as privacy. So lets hope when the dust has settled down we are left with a more secure and safe inte
30. 510.▲
    by pawadu 10y ago

    Because it allows you to install apps outside the official market? Using the same analogy would you consider OSX full of malware?