644 karma · joined June 3, 2017
I'm not saying that building a business is easy. But neither is building a career in academia. It takes many of the same skills.
You don't seem to know much about what academics do. A large part of their work consists of project planning, obtaining funding, hiring people to do the research work, advertise the results to get other people to contribute and so on. Only junior academics can really focus on the research. From a certain level of seniority, many academics are really research managers. It's very much building a business.
In preparation for the film, the director asked Christoph Hein, an Eastern German writer, to describe the typical life of a writer in Eastern Germany (which is what the film is about). At the premiere, Hein's name was included in the opening credits, but he asked to have it removed, because he couldn't see his story in the film. He described the film as being more of a dark fairy tale than a depiction of life in 80s Eastern Germany.
Haskell and OCaml are examples of real languages that use parser generators.
GHC: https://github.com/ghc/ghc/blob/master/compiler/parser/Parse...
Ocaml: https://github.com/ocaml/ocaml/blob/trunk/parsing/parser.mly
Then you should be able to do:
git clone https://github.com/livingcomputermuseum/Darkstar.git
cd Darkstark
nuget restore
msbuild
This should produce a Darkstar.exe below D/bin, which you can execute using "mono Darkstar.exe".On Windows, if you have Visual Studio, then you can just open D.sln and build the project.
bpftrace -e 'tracepoint:syscalls:sys_enter_open* { printf("%d\n", pid); }'
but then you can't access the arguments of the different probes uniformly, i.e. bpftrace -e 'tracepoint:syscalls:sys_enter_open* { printf("%d %s\n", pid, str(args->filename)); }'
does not work.You can do it like this:
bpftrace -e 'tracepoint:syscalls:sys_enter_open { printf("%d %s\n", pid, str(args->filename)); } tracepoint:syscalls:sys_enter_openat { printf("%d %s\n", pid, str(args->filename)); }'
This is a bit awkward, but it seems that this will be fixed: https://github.com/iovisor/bpftrace/issues/132 bpftrace -e 'tracepoint:syscalls:sys_enter_open { printf("%d %s\n", pid, str(args->filename)); }'
to show me all open calls as they happen. I would have expected to see an open when I cat a file, for example. But trying the one-liner, I only see a few opens of files in /proc.Can anyone explain what's happening?
"Here is a language so far ahead of its time, that it was not only an improvement on its predecessors, but also on nearly all its successors. "
Perhaps the hobby-archaeologist wanted to remain anonymous because unearthing historical artifacts with a metal detector is illegal in some places. In Germany one needs a permit at least and must leave finds undisturbed so that archaeologists can see the context of the find. If the hobby-archaeologist is searching illegally, then he/she may be afraid that the location of the find may lead to him/her.
I see the new electric Schwalbe quite often in city traffic and the acceleration of the thing seems insane.
The Schwalbe scooter was built in Easter Germany from the the 60s to the 80s and has achieved a sort of cult status. One still sees them today, even in the west. https://de.wikipedia.org/wiki/Simson_Schwalbe
There is now a new electric scooter that looks just like the original: http://www.myschwalbe.com/en/
https://www.anandtech.com/show/13279/amd-to-fab-7nm-cpus-gpu...
> “I'd emphasize that our technology is based on account behavior not the content of Tweets.”
There are many ways in which parsing can be improved in practice and theory. Actual technical aspects would be more interesting.
We do. Samsung used to have this on their phones (not sure if they still do):