dikaiosune

11 ms·

61.
by dikaiosune 9y ago
This particular announcement is about defining shared API types between libraries for which (I think) the things you've listed would be a concern. It's not a full HTTP implementation AFICT.
62.
by dikaiosune 9y ago
FWIW this is not the impression I've gotten from them. Of course, I'm not entirely sure what you mean, but I'm very bullish on their model and the people that I've met there are wonderful.
63.
by dikaiosune 9y ago
I found a job through them - they were very valuable. Putting me in touch with companies I hadn't heard of, wrangling interview schedules, etc. All great. Prior to working with them, it was challenging to even get phone screens schedul
64.
by dikaiosune 9y ago
uhhhhhh, multiple links in this block on the post: "That’s because I have been working on this subject for a long time now: * I did multiple talks on it * I even co-wrote a paper * I did it both as client and personal work"
65.
by dikaiosune 9y ago
Most distributions require that packages in the repositories are built with tools from the distribution.
66.
by dikaiosune 9y ago
First impression: fantastic section titles.
67.
by dikaiosune 9y ago
How much of the standard library works without GC enabled? How many community libraries do? D has a lot of great things (I am incredibly jealous of their metaprogramming facilities sometimes), but it doesn't seem like many people are s
68.
by dikaiosune 9y ago
The author is actually using it, to actually rewrite portions of C projects in it, and writing about their experience doing this in practice. For example, the linked paper is about using Rust at the I/O boundary in an existing, complex
69.
by dikaiosune 9y ago
Please correct me if I'm wrong, but don't Ada/SPARK's memory safety guarantees only hold when all memory is pre-allocated? My memory is that dynamic allocations aren't visible to the proof system (this may be in pla
70.
by dikaiosune 9y ago
In this case it seems the author is writing about the concrete results they've already obtained, not about something abstract.
71.
by dikaiosune 9y ago
I believe Firefox as of recent versions requires a Rust compiler to be available, and that's a pretty bread-and-butter application to have in your distro's package repository.
72.
by dikaiosune 9y ago
Can you be specific about which languages you include in the category of "fast and SAFE"?
73.
by dikaiosune 9y ago
From your endorsement of "using the compiler's symbol tables" (paraphrasing) I took you to mean that you're proposing binding directly to GCC (or another tool) as a library, relying on it's internal data structures
74.
by dikaiosune 9y ago
Agreed, that pipes+json is much higher overhead, just noting that this proposed approach still isn't free. > Let's get comfortable with what is good, rather than make what we are comfortable with? I agree in the abstract! I jus
75.
by dikaiosune 9y ago
> similar to what a current flagship phone has in terms of resources if not exact architecture. :)
76.
by dikaiosune 9y ago
I believe my phone runs a 64bit ARM with eight 2.3ghz cores and has the same amount of ram as the base Acer model?
77.
by dikaiosune 9y ago
The hardware in that Acer laptop looks surprisingly similar to what a current flagship phone has in terms of resources if not exact architecture.
78.
by dikaiosune 9y ago
There are already a lot of cases where LLVM can successfully optimize away things like safe Rust's bounds checks in loops. There are also efforts to include "const generics" which will let you use e.g. array lengths as generi
79.
by dikaiosune 9y ago
There's a lot of interest in formally verifying things about the unsafe subset of Rust, for example the Rust Belt project: http://plv.mpi-sws.org/rustbelt/ . One thing I've not well understood is how these eff
80.
by dikaiosune 9y ago
Not funny ones, in my experience
81.
by dikaiosune 9y ago
For anyone missing context, naming is hard. https://blog.expo.io/expo-sketch-expo-snack-a444f8dec72b
82.
by dikaiosune 10y ago
Expo | Software Developer | Palo Alto, CA | ONSITE, FULL-TIME | https://expo.io Expo (formerly Exponent) lets developers build truly native apps that work across both iOS and Android by writing them once in just JavaScript. It&#
83.
Expo Sketch → Expo Snack(blog.expo.io)
4 points by dikaiosune 10y ago|0 comments
84.
by dikaiosune 10y ago
At one point I made an attempt to do this from the CVE database, but it's difficult to do since CVEs aren't really machine readable from a "memory safety vs. other security flaws" perspective. I recall finding a lot of r
85.
Automatically Deploy Pull Requests for Create React Native App and Expo Projects(blog.expo.io)
11 points by dikaiosune 10y ago|0 comments
86.
by dikaiosune 10y ago
Posting a reply for @tsion, who seems to not be able to post at the moment: I interviewed on-site successfully at Google Seattle about a year ago, and I was given the option between writing code on a whiteboard or in a text editor on a Chro
87.
React Native support for Sentry(blog.sentry.io)
27 points by dikaiosune 10y ago|5 comments
88.
by dikaiosune 10y ago
Absolutely. Naming is hard.
89.
by dikaiosune 10y ago
https://www.adobe.com/products/sketch.html
90.
by dikaiosune 10y ago
Hi! Sorry for the very late reply, there's been a lot of interest and I haven't had time t get back to everyone yet. I'm very surprised to hear about the behavior you ran into with the loading messages on top of each other --

More ›