roop

6 ms·

1.
by roop 5y ago
I don’t know. You should contact Apple support maybe?
2.
by roop 5y ago
If you're using a USB hub/dock (the author says he isn't), you should upgrade to macOS 11.2.2 because: > macOS Big Sur 11.2.2 prevents MacBook Pro (2019 or later) and MacBook Air (2020 or later) models from incurring damag
3.
by roop 6y ago
> For commercial kegs, these sales are usually announced word of mouth, and I am not well connected enough to be in the loop I’d have thought if you had to be “in the loop” to know if something’s for sale, it means there’s a possible mar
4.
by roop 7y ago
The WHO situation report for 06/Mar says: > For COVID-19, data to date suggest that 80% of infections are mild or asymptomatic, 15% are severe infection, requiring oxygen and 5% are critical infections, requiring ventilation. Ventil
5.
by roop 9y ago
If your SDK is meant to be used as a binary framework or in any sort of compiled form (which is probably unlikely because you say it's going to be open source), I'd recommend Obj-C, because Swift's ABI is not stable yet. If y
6.
Reimagining the iPad split view for a Markdown editor(bisectapp.com)
1 points by roop 11y ago|0 comments
7.
by roop 11y ago
For the kind of applications that Swift is intended for now (i.e. iOS / Mac apps), debug-mode runtime doesn't affect productivity very much as long as runtimes are fast enough to respond to UI events. It might affect automated tes
8.
by roop 11y ago
> ... we learn that debug builds are often 100 times slower > than optimized builds (which themselves don't really > rival C). > Sorry, that's not the sign of a language that's > "
9.
by roop 12y ago
Here they are: Post on declarative style: http://talk.commonmark.org/t/571 Syntax diff: https://github.com/vfmd/vfmd-spec/wiki/commonmark-vs-vfmd
10.
by roop 12y ago
Thanks. Really happy to see that you're open to a complete rewrite of the stmd spec (to a possible algorithm-based style). I'll be happy to open a post in talk.commonmark.org on the ambiguity problems caused by using a declarative
11.
by roop 12y ago
With PEGs, it's not possible to express nested content, so we have to collate for example the blockquoted content of blockquotes and process them separately. Per my understanding (and I might be wrong here), part of the problem is that
12.
Evaluating the “Common Markdown” / stmd specification(roopc.net)
5 points by roop 12y ago|0 comments
13.
by roop 12y ago
jgm, thanks for your comment. I have a lot of respect for your work in Markdown parsing (especially your PEG grammars and Babelmark2), which I find useful and valuable. I understand what you have now is a provisional spec, but I have reason
14.
by roop 12y ago
True, we can write a CFG that can accept any input, but not one that can parse Markdown. Actually, I should have said it's not possible to write an _unambiguous_ CFG for Markdown. Say we need to parse emphasis in span elements. "_
15.
by roop 12y ago
It wasn't, but this is not a good way to build it either because (from my previous post): > A specification-by-example like this would have to keep an ever-growing list of corner cases and give examples for each of them. To get com
16.
by roop 12y ago
The problem is that there's no formal grammar and the spec of "Standard Markdown", while being more specific than John Gruber's, is still full of ambiguities. Some examples of ambiguities: 1. It does not specify preceden
17.
The reason behind Swift Array weirdnesses(roopc.net)
3 points by roop 12y ago|0 comments
18.
by roop 12y ago
Please see: http://www.vfmd.org/introduction/#prior-work
19.
by roop 12y ago
It's not possible to write a formal (non-PEG) grammar for Markdown. Hence, a spec, which is the next best thing (a la HTML5). Of course, vfmd is not a md-to-html converter, it's an md-to-parse-tree converter + a parse-tree-to-html
20.
Vfmd: Markdown with a spec(vfmd.org)
2 points by roop 12y ago|4 comments
21.
by roop 13y ago
That's funny. I am really a CS guy. Just happened to work for a semiconductor company for a few years after college.
22.
by roop 13y ago
Man, that's one hell of a clickbait title.
23.
by roop 13y ago
You mean they don't always have to be "voltages". Agreed. I only wanted to emphasize that at the physical level, they are not discrete. In this case, they happen to be represented as voltage drops.
24.
by roop 13y ago
Presumably, you're already familiar with how the text in your text editor gets converted to a binary representation. The code that gets stored in the iPad's flash memory is already represented in terms of voltages (See http:&#x2F
25.
Looking back at Stephen Elop's "burning-platform" memo(roopc.net)
2 points by roop 13y ago|0 comments
26.
Sharks and underwater cables (report from 1987)(nytimes.com)
8 points by roop 13y ago|1 comments
27.
IOS 7: Flat, or not?(roopc.net)
1 points by roop 13y ago|0 comments
28.
The Symbian Experience(roopc.net)
2 points by roop 13y ago|0 comments
29.
by roop 14y ago
Basically, this contraption seems to take a photo of the iPhone screen and prints that out like a Polaroid. That's basically it. All I can think is, "wtf".
30.
by roop 14y ago
_VMware should have a free upgrade program for recent purchases of 4._ They do. http://www.vmware.com/support/product-support/fusion/faq/lic...

More ›