skysight-inc/HackerNews huggingface dataset:
Which, perhaps ironically, is a small plot hole in the movie. "Wardialing" is not possible with a coupler - since the computer has no ability to hang up, or dial. When using a coupler, you have to dial manually.
"Contact", by Carl Sagan. It's not "light" and "easy", but it ties our current world to future promise. And it has some wonderful storytelling and writing putting this into context.

The main character, Ellie, is a superb and rich portrayal. Friends to whom I've recommended the book agree on this.

If you've seen the movie, it's an ok Hollywood production. The book is much, much more.
You obviously did not read the previous post or you don't know what HERE maps are.
Welcome to your average Javascript package -- does something trivial in the most over-engineered and expensive way imaginable.
That`s one of the really interesting questions in this. But if you look at polls on the policies which were supposedly so left wing they would turn away voters then another conclusion can be reached: namely that Corbyn`s left-wing policies are more in tune with the electorate and that this sabotage by HQ may have cost Labour the last election.

Someone should be going to jail for this.
Not the best review but I feel it is more for others looking to use it for things similar to the author (CFD).

It is nice to see some keyboard and screen improvements though. I am looking forward to mine arriving on the 26th and will write up a review from a software developer perspective if I get the time.
If the codec can not be implemented efficiently on existing battery powered handheld devices, it is pretty useless. That is the only metric that counts. Even if, it will take many years to a decade to spread, considering the replacement rates of those devices.
Oof. That is a heavy 6:40 clip of discourse. Thanks for sharing.
Here is a non-paywalled report on the same topic from another source:
https://inews.co.uk/news/labour-staff-deceived-corbyn-facebo...
I think that at the core of this problem is:
1.) Separate evaluation is done in absolute terms.
2.) Join evaluation is done in relative terms in a specific model. Which specific model? The model that only takes into account the union of features of both items. So this is similar to a relative comparison with conditional probability of occurrence.

The relative evaluation is done thinking about: In which situations would item B be more valuable than item A. All those situations are weighted according to the avaiability heuristic: easy to recall situations seem more frequent or important. To give a simple example: Perhaps a dictionary with 20000 words is enough for you, and you don't need a greater dictionary. But you can think than may words are in the 40000 words dictionary but not in the 20000 word dictionary, so the difference seems to be more important that what really is for you.
No offense, but I found your example code really confusing.

For the benefit of people familiar with Common Lisp:

* (= ...) is assignment, not equality testing
* (map list index-list) is equivalent to (loop for index in index-list collecting (nth index list)), or in a more FP style (mapcar (rcurry #'nth list) index-list)
* (map function list) is equivalent to (mapcar function list)

I think your example would have been less confusing if it used larger numbers to highlight where addition was happening and where indexing was happening:

arc> (= l '(4 5 6))
(4 5 6)
arc> (= f [+ _ 10])
#<fn: f>
arc> (map l '(2 1 0 0))
(6 5 4 4)
arc> (map f '(0 1 2))
(10 11 12)
Generators, a-la python for example, are completely equivalent to async functions and have nothing to do with IO.
> I don’t think the FOMO is linked to Internet usage…

Evidence suggests otherwise: https://www.sciencedirect.com/science/article/pii/S235285321...
I guess that’s it. I bought my first Mac in 2010, a 13” MBP for £800 and sold it in 2014 for €600 which made it a fantastic value machine.
> In these cases, Go's model does not work well.

I don't think there's anything about Go's concurrency model that precludes bare metal; I think it's just that the maintainers didn't want to support a bare metal runtime. In fact, I recall at least one other project that modified Go's runtime to support exactly this. I'm also not sure how much of the C interop overhead is due to the different stack models and how much is due to GC concerns or other things. But generally I agree with you--in practice Rust is well suited for these types of tasks and Go is not.
I can’t say I’d find that sufficient, as “whatever we can” is subjective, and I value my own life over the assets and existence of some faceless legal entity. OTOH, I would not take a job or assignment where this was a consideration.
Absolutely. The latter two books have a different feel but are as impressive as the first in different ways.
That's actually wrong to say Trump didn't do anything special. Trump had almost 63 million votes which is more than Romney's almost 61 and McCain's almost 60.

Hilary had 65.8 million which was almost exactly what Obama got in 2012, 65.9. To say that Trump did nothing is the same narative that Bernie supports started blaming Hilary supporters for losing. It's always the people that vote at fault and not the people who didn't vote.
I think there is something compelling about the combination of a shallow initial learning curve and optional elements like static typing that can improve maintainability for more complex projects. The shallow learning curve makes it easy to get started, then once basic familiarity has been established, one can move on to code that isn't as 'clean'.

'Optional' is key there. Don't want to use type checking? You don't have to.

It's a bit like how some video games introduce one skill or gameplay mechanic at a time, which helps keep players from being overwhelmed by new concepts.
How to Use a Jailbroken Fire TV Stick
I think the connection is that when you're 100% of the pie, you're, by definition, average. You cannot be exceptional when you so dominate the market segment.
The reasoning why this exists is in the very first paragraph...

> Python’s lack of safety
guarantees can be problematic when, as is increasingly the case, it is used for
critical applications with high correctness demands. The Python community has
reacted to this trend by integrating type annotations and optional static type
checking into the language [20]. However, there is currently virtually no tool
support for reasoning about Python programs beyond type safety.
FxFactory Pro 7.0.1 Full Crack and Keygen for [Mac+Win] Here
But it's a binary decision -- do they have a degree or not?
Touch Bar kills it.

I am a touch typer. I use the escape key constantly. I use the function keys frequently. Like every other touch typer I know, none of us want to look at our fingers to type anything, let alone to look down and navigate around a microscopic touch screen menu that requires you to not only look at your fingers but to move your hands away from the micro-screen to see what you're trying to tap on. I have no idea how they decided any of that was a good idea, let alone for a machine aimed at professionals.

I'm thrilled to see 32gb RAM finally, but I'll pass. Wake me up when they remove the Touch Bar.
Note that this post is from April, and a lot of experimentation and reams of discussion and debate have taken place regarding the details of the two RFCs in question (along with other related RFCs such as the one for the Pin trait). In fact, one of the RFCs linked at the top of the OP has been closed and superceded by a newer one: https://github.com/rust-lang/rfcs/pull/2418 . I've actually heard that tomorrow (Monday) the futures and networking working groups will begin a series of regular blog posts on design and implementation leading up to the release of Futures 0.3 (which IIRC intends to be more-or-less the final design for Futures 1.0).

As for this article, I think the broad implementation details that it talks about are largely still accurate, just don't take it as gospel. :)
Android for Africa
Definitely. We’re currently blocked with the builtin await using thread local storage, but that’s planned to be removed and replaced with something that will work without an OS before stabilisation.

I have had the old macro based async code in Rust running on a Cortex M device, completely runtime free. Once the TLS stuff is sorted I plan to port this forward to work with the builtin syntax.
I've been combing over the reviews on youtube and I came across this link [0].

> A teardown of the hardware on Friday, however, reveals a new silicone membrane encases each key that potentially serves as a dust-repelling feature to protect against malfunctions.

I'm going to give it a bit, but if it turns out to be the case that for dust at least the problem is resolved. They'll definitely get a purchase from me. I'll have to get used to the reduced travel after working with a late 2012 for 5+ years!

[0]: https://appleinsider.com/articles/18/07/13/2018-macbook-pro-...
I think the issue is that articulating that balance is hard - for example, the original thinner retina MBP lost some practical usability, but from a work standpoint for me, it was worth it for the increased portability.
This is a fantastic summary, thank you! I use disposeable mails all the time, and any company that refuses to accept them either gets a bogus hotmail account or (more likely) loses a chance to show me what they've built. Otoh, if I want their messages I will leave an address willingly - not my main address of course, but an alias.
C++ has futures libs too. See the Seastar framework, for an example.
Truthfully, it's why I'm very sad that the Air looks to be discontinued. I'm still using a 2012 MacBook Air, and it was quite possibly the least stressful computer purchase I ever made. $1000 and some change to get a computer that has just worked magnificently for nearly 6 years now without missing a beat. I walked into an Apple Store, told the Apple employee I wanted a 4 gb MacBook Air, and in 5 minutes I walked out with one, no other pressure or sales pitches.

It was a very relaxed experience for me, and I certainly hope that it's still the same with Apple. $1000 isn't chump change, but it's accessible for someone just a little above the poverty line like me.
If you enjoy writing those things, it's actually better since you're getting more motivation to work on it. You actually like making it, so it's much less draining and much more satisfying.

Also, you only write what you need. Honestly I can never find a library that is good enough for what I want to do. Games have so many possible features that it's impossible to cover them all with good libraries.

So it's better to aim low, with simple enough features, and make them yourself so that it's tailored for your programming style, and for what you want to do. You're not reinventing the wheel (I'm not talking about making a graphics of physics engine).
For those of us considering upgrading from an older Mac, it's quite useful.
king_nothing did not say his great-grandfather "invented" anything. He said his great-grandfather made it.
William McBride, Who Warned About Thalidomide, Dies at 91
This is dangerously close to becoming a standard talking point nthis topic. It’s dangerous because it’ll be wrong as soon as anyone implements an encoder with speed as an objective, and especially when dedicated hardware starts to appear in devices (about 12 to 18 months from now)
Yes, I suppose maybe you'd probably have a file per VBO or whatever. Create a dynamic one: it's like a pipe, write- and append-only. Create a static one: it's like a file, and you can mmap it (like glMapBufferData), or fseek+fwrite to it (like glBufferData), and maybe fseek+fread from it too (because why not).

The command queue would be a write- and append-only pipe, containing of state setup commands and rendering, in some format that could be efficiently transformed by the driver into the actual commands that would get sent to the GPU, since this hypothetical queue would probably be GPU-agnostic. (I think this was how D3D9 worked internally, and that may still be true for more modern versions...)

(You wouldn't have commands for modifying buffers. That would be just something you do yourself by accessing the buffers. As the creator of the buffers, you know where the data is inside them, so you'd just replace the data in question with new stuff.)

Anyway, even if in practice this wouldn't be optimal, it could probably be made to work well enough. A file-based approach is at least not ridiculous to imagine.
Political leaders don't lead troops. They lead department heads in decision making. In that field, good ones operate the same way: leading from the front, showing willingness to take risk on themselves, supporting their direct reports as needed.

Similarly, Generals don't (usually) lead troops. They lead company commanders.

And so on.
Yea, that's what gets me. Maybe I need to evolve, but to me the 'Pro' in MacBook Pro means you do not look away from the screen while working.
They way these annotations are used is really not part of the language. I prefer to view it machine-checkable documentations. It's more light-weight an higher level than your C/Java type systems.
I think that being async-by-default makes sense for any new high-level language written these days, but the machinery required to make that happen is probably always going to be magic enough that there will be some space for low-level languages that will find value in giving the user choice between synchronous and asynchronous operations.
Easter Island statues may have 'walked' out of quarry (2012)
Been using way too many apps in the past twenty years. AskSam on Windows in the 90s until early 2000s. Then they stopped developing it. Exported my notes in HTML format, waiting to be migrated into my latest tool. - Then when the iPhone arrived tried to do note taking on it. Used Momonote app (still exists, but practically abandonware), created a couple of thousand notes. Exported them as csv, waiting to be migrated... Then Evernote. Excellent tool. I have 12k notes in it. Love it. Still use it. Paying member. In between tried to migrate from Windows to Ubuntu. Started using Emacs+Org (several hundred notes in there, waiting to be migrated). But also ZimWiki. Then moved to Mac/OS. Went back to Evernote. Currently using a combo of Evernote and Bear Writer app. Love Bear. Has a phantastic UI, markdown, super fast interface, syncs with all my iDevices.

But I am aware that in twenty years from now none of these tools might be alive anymore. I keep exporting and backing up my data because of this. And my backlog of "to be migrated" grows longer and longer.

For now I find it more convenient to use a tool with a sleak interface that offer all the features I need in a "personal wiki" / note taking app: inserting screenshots into notes (this is a killer feature for me), beutifully rendering my markdown text, fulltext search, nested folders (or tags in Bear lingo), syncing across all my devices. The alternative is too cumbersome: For instance Emacs/Org + rgrep + Dropbox for syncing + git + a bunch of .emacs entries that allow me to insert screenshots.

Edit: Forgot to mention IdeaNote. Used it when I tried to replace my iPhone with a BlackBerry device. Excellent app. I could create super long and time stamped journal entries / logs / notes on the superb keyboard of the BB device in seconds (never got used to typing on a touchscreen). But eventually the BB got abandonware itself. And so the app. Luckily I could pay 50$ to export my 3k notes. Migrated them successfully to Evernote with a bit of Ruby script.

Edit 2: Lesson learned for me: No tool is going to be there forever. Need to have a clear concept for how I will keep my data independent from tools du jour.
Is PicoLisp the same?
Elon Musk Calls Diver in Thai Soccer Team Rescue a Pedophile
I really like how Vinge addressed the Fermi paradox by permitting that the constants of physics may not be different in different parts of the galaxy.

The first chapter (via Audiobook) was one of the best first chapters I've ever read / listened to. I was totally hooked after that.
Control is another reason. You relinquish control the more moving parts there are. If you ever looked into the tokio stack you realise there are a Lot Of Stuff going on.

Which doesn't mean it's bad. I'm excited about tokio and rust's async story. But I love that I get to choose.
Yes, by about 50% and 30%, respectively. See the graph in the article.
I knew the older and younger ones always had it in for us!
It's a huge guinea pig for .net, windows server, and azure - a perfect example of eating your own dog food.
Cons: Keyboard, Touch bar, lack of ports, cost

Pro: Great display. Build quality. MacOS

It's too bad all the cons except cost are new to the latest generation ( post-2015 ) MBP.
If you think there’s a risk of comments becoming outdated in a config file, then the risk of it becoming outdated in a separate place seems even higher.

Configuration via environment variables is as far from best practice as I can imagine. It prevents proper validation of settings (e.g. a typo can’t be detected because you don’t know which environment variables are used by other programs), not to mention the possible security implications. Besides, these environment variables would have to be set somewhere, like a startup shell script, which I bet would end up with explanatory comments anyway.

This trend of using environment variables is a result of trying to make applications stateless, therefore easier to run in containers. However with something like K8s ConfigMaps, it seems totally unnecessary.
> Marketing for a service you have registered is not spam

From a legal standpoint, this is broadly true, but I'd say from a user's perspective, this is only very narrowly true.

For example, if I'm receiving an advertisement for a product that I "freely" trialed but subsequently rejected, I perceive it as spam.

Reputable companies provide an "unsubscribe" feature that actually works, but it's impossible to determine a priori which companies those are, and, more importantly, if they'll still be that way when that first e-mail arrives.

Really, the most trustworthy behavior would be to assume I'm consenting to precisely one follow-up email regarding my free trial, rather than an open-ended subscription. Until that's either industry standard or regulated (in a way where individuals can easily recover money damages), then I'm still using disposables at first contact.

> More and more companies deny registration from Disposable Email Addresses. Because these users are worthless.

Encountering a company like that, I assume they believe the second assertion to be true because the sole value of the users is as advertising eyeballs due to the product trial itself demonstrating no value. In that case, I don't bother.

I will, however, usually make at least a modest effort to try a few non-Mailinator disposables.

Although Mailinator has alternate domains, they've made themselves very easy to block, because a simple DNS query reveals the MX to be mail.mailinator.com. Just one more level of obfuscation (e.g. making the MX for streetwisemail.com be mail.streetwisemail.com and just have the same IP as mail.mailinator.com) strikes me as a good Pareto-principled step.
How Managers, Coworkers, and HR Pressure Women to Stay Silent About Harassment
What’s the TLS stuff to be sorted out?
Webinar – Cómo vender en Facebook sin pagar
This is me waving to the Apple bots!
The ~2016-designed [0] third-generation butterfly keyboard (MacBook Pro 2018) features a silicone membrane [1] designed to «prevent and/or alleviate contaminant ingress» [0] thereby softening or preventing dust-caused key failure.

[0] http://pdfaiw.uspto.gov/.aiw?docid=20180068808

[1] https://ifixit.org/blog/10279/apple-macbook-keyboard-cover-u...
HEVC/H265 implementations were initially very poor also, but it doesn't mean much now.

Plus, mobile devices will use embedded fixed-block ASICs for this, just like they already do for every existing codec. All codecs are completely impractical on mobile devices if you're basing your estimates off software numbers, even extremely well optimized software will kill your battery. So it's basically meaningless to try and extrapolate from optimized numbers, much less preliminary ones.

Besides, encoding AV1 is what's expensive, but mobile devices also do not necessarily need AV1 encode support anyway. They will need decode support. Slow encode support is going to be a problem for people creating and serving video. But better compression rates from AV1 substantially help mobile devices, too, by reducing bandwidth needs for providers. You're likely to see major video content providers taking the hit of AV1 encoding, while users only need to decode, and this will largely be how it is used.
How AI is being used to boost the creative process – Industry Trends – IBC
I don't think it's betting against yourself. It's just allocating some funds to an alternative version of yourself that has had bad fortune. You can think of it probabilistically.
"The reason they can't tell you is that you may then 'kidnap' yourself to collect on it."

I don't think you know how this insurance works.
h265 had the exact same problems too. AV1 is not implemented on mobile, yet. Both Apple and Google are on board with this, as soon as it is completed I believe it will spread quite quickly.
Not sure why this was down voted. It really is the only thing that matters.

The trend is overwhelmingly towards mobile being the dominant platform for video. And if your videos can't play on the majority of the iOS and Android it's simply a non-starter. Look at what happened to Flash once Apple banned it on iOS.
It looks over-engineered, complicated and non-intuitive. In 90% of cases, vanilla business logic will be concise enough. I've used validation modules like Meteor's check[0] before, and I think that's a good example of how much surface area a validation library API should have.

[0] https://docs.meteor.com/api/check.html
Take a look at parallel simulation codes (for example, LAMMPS in chemical physics).
”I honestly think Musk was trying to help. He does this stuff everywhere, Puerto Rico, Australia etc. it does seem PR”

He may have been trying to help without consideration for how the world thinks about him and his companies, but it became PR the moment he tweeted about it (if John Doe tweets he’s donated to charity X, i consider that PR for John Doe, too. If he just wanted others to donate, he could have tweeted “X does good stuff and needs money” without mentioning his own good deed)
for any particular company, it (big payout for executives) only has to happen once, after that they (execs) can leave/retire/sellout

take any particular company and multiply it by the size of the whole market and you see what we see today: short term thinking across industries, LBOs, big bonuses for executives even in failing companies (toys r us etc)

so, while in any one particular company, yes shareholders wouldn’t put up with that behavior long-term, across the whole market they still get payouts, still have more stable investments that pay dividends etc even if there are those bad actors that wreck companies for thier own will

slightly off-topic, but, for every company that maximizes it’s short-term value, there is usually collateral damage to the people who work there (and thier families), sufferimg low wages, bad conditions, mass layoffs)...that to me is the real issue...
I see the number of children a couple has as a vote on how many people should exist on earth. If you have 0 or 1 child as a couple, you are voting that there should be fewer people. If you have 2 children, you're voting that there should be about the same number of people. If you have more than 2 children as a couple, you're voting that there should be more people on earth.

With that context, I can clearly see why nobody in a city would want to have more than 2 children.
Very interesting! I was going to propose that maybe this is why watching sports (including esports) is not something I am the least bit interested in.

I was going to say, maybe my brain doesn't work like it's supposed to... but maybe I just never got into it.