1,521 karma · joined August 13, 2015
[1] https://en.wikipedia.org/wiki/Explicitly_parallel_instructio...
If the environment you run on doesn’t support JIT compilation (iOS for example), AOT compiling WASM is useful.
as a developer, not a user. I can’t have two different apps running on different displays, nor can I take advantage of the display’s resolution. In practice, everything is mirrored.
> Almost all apps obviously take advantage of the keyboard
When I say take advantage of the keyboard and mouse, I mean to offer shortcuts/navigation akin to what you’d find on a desktop.
I don’t mean to say that apps should be exactly like desktop apps, but the iPad UX is making it harder to use the current iteration of document/spreadsheet apps.
There are things the iPad does strictly better, of course. But I don’t see these experiences as mutually exclusive.
My original point was that productivity apps, whether its photo/video/audio editing, word processing, or 3D modeling, all categorically benefit from features like better file management, IPC, background processing, working with external displays, easier keyboard/trackpad navigation, etc...
I saw some things in the presentation around external storage and thunderbolt devices which look like steps in the right direction, but the OS is really not doing it any favors. I would guess that the iPad is successful among this demographic despite iPadOS, not because of it.
Apple should be trying to empower users with safe abstractions, not lock them down even more.
For example, there's no notion of rendering a video in the background, organizing project files independent of the application, a plugin ecosystem for creative software, and proper IPC between these apps. So even though the market is different, there's still a lot to be done to come close to desktop editing workflows.
Even still, the level of finesse they have with Excel and productivity software on a desktop OS was just not replicable on the iPad. It pained me to see my Dad work on his spreadsheets on the old laptop again.
The silver lining to this is at least the iPad is good for watching videos and pretty decent at web browsing. They still use the device casually.
Take Excel for example. Try right-clicking on a cell or dragging down a formula, and you'll see that it only picks it up a fraction of the time, and you have to click multiple times with gesture-like latencies in between to get it to work.
I do still prefer Sublime for the specific use-case of opening a random text file. Its startup time is far faster than any other editor.
We only care about the specific subset of programs that the compiler is able to prove properties about. https://en.m.wikipedia.org/wiki/Termination_analysis
They don't even attempt to distinguish the size of the stack from the rest of the runtime.
Yes, I know about iTunes Wifi backup, but I'd rather not be on my home network for this.
The goal is to treat the salary as a necessary (evil?) for "what you need to feed your family, buy a house, etc..." and not as the primary motive for work.
An employee who makes a valuable impact does so because they want to see the company/product succeed.
- X type of employee is more valuable than Y type of employee, therefore they should be paid more.
- There is no mechanism or incentive for growth (a.k.a the career ladder argument).If you're thinking about using it, consider instead:
- strlcpy() if you really just need a truncated but
NUL-terminated string (we provide a compat version, so
it's always available)
- xsnprintf() if you're sure that what you're copying
should fit
- strbuf or xstrfmt() if you need to handle
arbitrary-length heap-allocated stringsRegular expression syntax is context-free anyways, so they could use grammars if they wanted. Then again, you have to wonder if all of this should be covered by a theory or PL class instead.
A more relevant goal of error-tolerant parsers that can respond quickly to incremental changes is still a wide research problem.
Some argue that parsing is a microcosm of the rest of the compiler, since it requires one to transform a program from one representation to another. However, this message doesn't really come across when you're operating on highly unstructured input, and not doing any simplification passes.
I think execution is really important for visualizing the effects of your work.
If unicode was an external library, it would be my responsibility to update this identifier parsing library.
It's nice to see the float parsing speedups too.
I do wish the Unicode package wasn't tied to the Go release cycle. Unicode 13 was released in March of last year.
Special props to Ian Lance Taylor and Robert Griesemer for their continued revisions of drafts, and exemplary discussion with the community in implementing feedback.