It's also a niche, specialist hardware project made in extremely small quantities. They probably should have charged more, not less.
508 karma · joined March 4, 2009
It's also a niche, specialist hardware project made in extremely small quantities. They probably should have charged more, not less.
If you support Python 3.10+ you can do this far more cleanly.
The home page of Rebol, which it says it's derived from, seems to do a much better job at stating its purpose: http://rebol.com/
Perhaps that's okay, I don't know, but it seems strange that the little pieces of client-side javascript are so copyrightable yet this other work isn't.
I think both "wait" and "interrupt" culture etiquettes involve supporting the current conversation, not ignoring the other person's input. The latter is frustrating in both styles.
What plugins do you have installed? Maybe one is slowing it down?
And perhaps run “clear caches / restart” just in case there’s cache corruption
I run it fine on a Linux machine that has 4GB ram total — I’m curious how much memory you’re talking about.
I can't speak for Rubyists, but I find it a very strong complementary skill to Python, as it allows for writing things that are impractical in Python. And Rust feels friendlier as a Python-complement than C. Especially parallel C.
Receiving a compiler error in Rust is more appealing to me than debugging a segfault or race condition in C, especially since Rust will always tell me when one exists. Or more importantly, I can feel comfortable pushing new fast low-level code to production knowing it's not a risk. There's no ambiguity. "fearless concurrency" is not just a buzzword, it's partly what makes Rust fun and practical (for me). As well as the incredibly-fast start-up time of my Rust code compared to Python.
It is also appealing for Python programmers because of the increasingly-decent support for mixing the two languages without overhead, including publishing pure-Rust packages as python modules^1
If you switch between layouts while learning, you'll maintain that ability to switch. Similar to how the brain can switch languages.
I found this to be an easier way to learn, as it didn’t interrupt life as much. All of my work stayed in Qwerty until my Workman was good enough. And I still use both.
Edit: The one frustrating switch is Workman's moved copy-and-paste keys. I do press the wrong ones by accident. I would choose Norman instead of Workman today purely for that reason.
#[global_allocator]
static GLOBAL: MyAllocator = MyAllocator;And the second definition of professional “a personal who engages in an activity with great competence”
These are implied by the question that begins the article: “Why is it that some people seem to be hugely successful and do so much, while the vast majority of us struggle to tread water?”
The author could have chosen better words, but I feel you’re missing most of the article by focusing exclusively on them.
I agree with slower, at least for computational tasks, but not security. Do you feel safer installing an organisation's native app than using their web app?
> The only positives are to corporations and institutions with profit motives...
What advantage does the web give to corporations that native apps don't? You mention spying, but the native mobile app ecosystem is filled with tracking and analytics code (and it's easier to hide it). The only corporation-level difference I can see is that native apps are heavily tied to a specific company's platform, while web apps aren't. This is a huge positive to the web - I've felt free to change platforms many times.
A second huge and underestimated positive of the web is backwards compatibility (ie. lower maintenance headaches). A complicated internal web app I wrote eight years ago is still running despite not being modified. The websites and lousy javascript I wrote as a kid in 1999 still run exactly the same as in 1999. Spacejam.com is unmodified from 1996. Yet I have many native apps from two years ago that no longer run correctly due to OS updates (especially on mobile).
- In your first example, foo is of type "Bar"
- In your second, foo is of type "function that returns Bar".
ie, if you stored your foos in separate variables they would be:
let my_var: Bar = ...
vs let my_function: fn() -> Bar = ...
If they were to change it to your suggestion the latter would be either awkward (multiple colons?) or inconsistent (different syntax for types and declarations).(Almost?) all other other major vendors at the time used it heavily too: Microsoft Office until 2011, FileMaker until 2010.
If Apple released the OS a year earlier, but without any available third-party software (waiting for almost-rewrites to happen), would they really have been better off? At this time they were on life support and would have had difficulty convincing third-party vendors to invest heavily in their platform, or to convince users to adopt it without any major applications available.
In either case, Adobe's sway clearly declined over the years, as Apple cancelled the 64bit version of Carbon while Adobe was still heavily built around it, forcing Adobe to switch (and an awkward year or two when the Mac, but not Windows, versions were stuck with 32bit memory limitations)
> Not watching CNN won't prevent other CNN-watchers from talking to you.
I think a conversation with a CNN-watcher is more interesting when you yourself have read slower sources than if you have both spent your time watching live broadcasts or reading live articles. You'll find you both have different kinds of points to bring to the conversation.
I've found a large difference between the daily (or 24-hour) sources and weekly/monthly publications. The latter are more removed from the day to day events, and so tend to spend more time on the issue itself and wider trends, and less on personality clashes or rare, once-off outlier events (which by definition, you don't need to be worried about^[1]). Relying mainly on them, you'll have heard less about what has happened in the last 24 hours, but likely know more about the major events and wider trends of the past year. The daily sources are particularly bad at portraying those wider trends: they will show a violent crime every night regardless of whether a hundred or only ten occurred.
[1]. The truly significant outlier events will still be covered by the slower news cycle and in normal daily conversations. There's no risk of not knowing that a 9/11 happened. I haven't found that it matters if I don't know about the latest disaster immediately: to the contrary, a conversation can be stronger when the other person explains in their own words what has happened, and I can ask questions with genuine interest.
Note that he's not advocating being oblivious to the world. See the third paragraph:
> To be clear, I’m mostly talking about following TV and internet newscasts here. This post isn’t an indictment of journalism as a whole. There’s a big difference between watching a half hour of CNN’s refugee crisis coverage (not that they cover it anymore) versus spending that time reading a 5,000-word article on the same topic.
Edit: after a quick Google search: "Jan 29, 2004 - Sandisk ships world's first production 1GB SD card"
(beats it in Sunspider, is roughly equal in others)
And it maintains the lead in ECMAScript6 support: https://kangax.github.io/compat-table/es6/
I think his writing has two particular things going for it:
- He explains concepts clearly with understandable examples.
- He presents concepts that aren't (or weren't) well known outside of academia to a wider audience.
HTTP2 requests have (sometimes significantly[1]) less overhead, and most sites following good HTTP/1.1 practices still make many requests.
Open the network panel in your browser and view a few large sites. Despite minimizing requests with sprites, concatenation etc, most still make dozens of requests, with some large sites pushing over a hundred.
(for example, I just loaded a page for a single tweet on Twitter and it involved twenty requests, with a size over 2MB.)
I think your list of options are incorrect:
- You can optimize for HTTP/1.1 and it will be fast over both protocols.
- Or don't optimize, and it will be fast over HTTP2 and slow over HTTP/1.1. The main benefit is saving development time & complexity. This will not be a worthy tradeoff until HTTP2 is more widespread among your users.
[1] The reduction in latency can be massive, for instance, as the HTTP2 server can push resources immediately without waiting for the browser to request them.
The article is misleading on this, but those HTTP/1.1 best practices aren't slower when served over HTTP2. HTTP2 will still be faster than HTTP/1.1.
- Spriting and concatenation will not be worse under HTTP/2, just (mostly) unnecessary.
- Splitting content across multiple domains will be 'harmful', in that you're enduring multiple TCP handshakes instead of one. But this is no worse than HTTP/1.1
- Minification is unchanged. It will still decrease the download size. Although I sometimes find that the difference after compression is trivial on many modern sites, so is often not worth the decrease in readability/debuggability.
They designed a new compression algorithm called HPACK specifically to compress headers in HTTP2: https://http2.github.io/http2-spec/compression.html
In small HTTP/1.1 requests the headers can be much larger than the content, which is part of the motivation for combining files into one request.
The size difference over a wire between gzipped/deflated text and protocol buffers is also usually dwarfed by almost any other asset being loaded on the page (images, fonts, videos etc).
The benefits of human readability and simplicity probably outweigh those size differences, I think.
I do agree there's a lot of room for improvement in the html/css/js combination, though. They were designed for far less dynamic interfaces than those we're trying to build today.
The CSS model in particular is very conceptually complicated for a layout system. I say that having used it for 13 years.
Things may have looked very different had they continued the heavy development pace after releasing IE6. IE had a fast and modern engine compared to contemporaries when IE6 was first released, but then it went five years without any major updates.
I'm undecided about Google's growing browser control, but in any case I don't see Google making the same mistakes as Microsoft.
Otherwise RHEL/CentOS have longer support periods (ten years).
An open source browser can conform to the W3C DRM standard ("Encrypted Media Extensions") and remain open source.