jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
I've been using Signal for years now and although it still has its flaws (requirement for a phone number, PIN number debacle), it is IMHO the best alternative and I've moved my sginificant other, friends and families towards it.

Combined with signal-cli (https://github.com/AsamK/signal-cli.git) you can easily set up your own files & messaging upload. For instance, I've created an automatic upload to a Google Photos album for my family group chat and they love it !
Forget about them all and send a regular SMS message. If the above doesn't work for essentially no cost then your phone provider needs to get it's head out of it's rear and stop raping you... There is no excuse for the way phone companies charge...

If you need anonymous, then none of the above really work either.
That's been like that for a long time, several times a month I receive a notification that someone I know comes into Telegram, and even my close family is going into Signal bit by bit.

But yeah, here whatsapp is the biggest one still and too many people are using it.
How would this work in practice? Voters post to a publicly accessible append-only database from a personally owned computer? Can this be implemented on paper ballots?
You can also find the project on GitHub: https://github.com/makers-for-life/makair
half the country hangs on trump's every word. to look at it from the other side, consider two Democrats running for office. one gets Obama's endorsement the other gets tarred and feathered. which one stands a better chance to win?
Sorry but how exactly are you going to enforce that?

It’s like saying we should not have let news to be carried over the internet.
The whole thing will get incredibly hot. Absorbing laser energy. And the powder management is a huge pain in the ass. Powder can’t be reused forever, eventually some of the partially fused portions will have to be filtered out by a secondary process. All solvable problems of course.
Perhaps it happens for everyone but in some cases, you black out and forget it.
Um, because those engineers don't have commit access to the repository? You can't just hire an engineering team and take over any open source project you want.
Thank you for the detailed reply. I'll try it out (in a VM first).
The biggest problem here is sharing your IP address. I do not want the FBI at my house every time my neighbor downloads something illegal (recent cases show that this does happen). Some level of protection is necessary. NAT for example seems a poor choice. Maybe with IPv6 the FBI would know not to bother the network operator but to go directly to the offender. Or maybe some sort of a part-way link level encryption gateway is the answer.
These are interesting comments from Nokia in the light of their partnership with Microsoft. Most likely this would mean Nokia will change the UI of the Windows Phone environment to their taste.

Secondly: According to Nokia, Microsoft will be adopting Ovi Maps to all their services in the future.
Yes, and she was in a relationship for six months after the lie and failed to realize he was still married. (Or, she lied)
Yeah I'm sorry, but web views are incredibly substandard to native apps. I've never found I hybrid app that I found comparable to its native counterpart. Simple things like scrolling can be very spotty most of the time.
> Yeah I was really just trying to point out that the marketing on the main page can be improved. I get that OOP can be a selling feature, but the other four not so much.

It's a totally fair point.

One thing I'm trying to keep in mind is who I'm marketing to. Right now, since Wren is so young, the people whose attention I want are not end users. They'd have to be half crazy to use Wren in its current state in a real application.

The people that will take an interest now are those that are keen on new languages for their own novelty's sake, or that are interesting in contributing to Wren itself. That's the audience I had in mind, and I think the bullet points make a bit more sense when you consider that.

Definitely, when Wren gets more mature, it makes sense to refocus the initial verbiage on what it can do for and end user.
OK let's say you have f, it only takes arguments a:Y, and b:Z.

I call f(Z, Y). What happens? Does the machine segfault? Probably not.... so you're in "check the types at the callsite" territory. And honestly those kind of boundary checks are the problem, so to speak.

Are we doing static analysis of the entire codebase (a sort of closed-world theory?) You could maybe do something like this for non-exported functions, though at the V8 level that's tough.

I think that there would be possibilities to somehow get systems to be set up in a way to do more cleverness along these lines, but so long as you're taking in stuff from the outside world you end up needing to set up relatively costly checks, relative to the cost of the "default" JS semantics that you're trying to avoid paying.
The goal of pruning back to the minimum syscalls and runtime libs for dependencies would surely be OS agnostic: I want to ask "for BSD?" in all seriousness because it should not be a problem to do this for any OS.

Given access to the source, the new W10 being visored, I would even ask if this could work in hypothesis for Windows but I suspect the nature of the OS is more intermixed dependencies than UNIX derived OS. But.. you never know
I think you're misunderstanding the article you linked at least a bit here; it's not the origin story of Apple's original one-button mouse. It's describing the "no button" Pro Mouse circa 2000, which still functioned like a one-button mouse in practice. Macs had one-button mice since they first shipped in 1984.

> As far as not thinking about a button to click - that only works if the idea of 'right-click' doesn't exist.

Well, when you adjust your timeline back to when that first one-button mouse came out in 1984, one can argue whether the idea of right-click as we know it today really existed! There were multi-button mice already, but there wasn't any standardization as to what the buttons did, so Apple's insistence on "there is just one button and it does THE THING" was at least defensible. And IIRC early versions of Windows pretty much ignored anything but the left button, although applications could receive clicks from them. I'm pretty sure the "right-click for a context menu" idea that's become standard today actually started with OS/2.

> In the real world where it does now you just have to know to control-click, which seems strictly worse.

Or you could just right-click. :) Every mouse Apple has sold since 2005 supports right-clicking (and OS X actually supported right-clicking from the start if you plugged in somebody else's mouse!). Their trackpads lets you click with two fingers for a right-click effect.
Thank you, now that basic calls are working we will definitely put more effort in the look and feel.

We also plan to allow some basic customization like adding a logo and selecting 1-2 colors so you can make the Jam better fit the identity of your community (a bit like on reddit).

Appreciate the suggestion of switching the "about" and "create room" segments, great idea!
Because to change Bitcoin means to fork Bitcoin, and 2017 has shown that the community does not want to hard fork to update the consensus of the chain. A bigger question is how will Bitcoin deal with securing the chain once miners rely primarily on transaction fees; especially considering Bitcoin can't scale. Another factor is that spent addresses release public address information which is susceptible to quantum attack exploits. I'm bullish on cryptocurrency (like Ethereum) but bearish long-term on Bitcoin. However, one thing Bitcoin is used for currently is as a decentralized collateral. You can wrap Bitcoin and deposit it on Ethereum and lend it out for interest. This is a fairly good use case in the short term, but Bitcoin the blockchain is not sustainable longterm.
How is the offering from companies like UiPath any different from “macros”, such as AutoHotKeys or Macro Express?
> I think New York actually has worse problems with crime and homelessness than SF

And you’d be dead wrong.

https://www.baruch.cuny.edu/nycdata/public_safety/crime-sele...

I don’t know how you could even think that.

https://www.nytimes.com/2017/12/27/nyregion/new-york-city-cr...

https://en.wikipedia.org/wiki/Callahan_v._Carey?wprov=sfti1

> I watched as over a hundred people walked past and sometimes over him.

Have you ever walked through a mid-market BART station?
Ah nvm, 2nd gen was in 2015.
There are some companies that are paying people to remove carbon from the atmosphere, but yes, we absolutely need more of them.

Stripe has become a huge leader in the space with Stripe Climate: https://stripe.com/climate

Microsoft is investing $1B into their Climate Innovation Fund to help them remove all of their historic carbon emissions by 2050: https://blogs.microsoft.com/blog/2020/01/16/microsoft-will-b...

Shopify is contributing $5M annually to remove CO2 from the air: https://www.shopify.com/about/environment/sustainability-fun...

And there are many other examples of big corporations stepping up to undo some of the damage done to the planet.

In the public sector, the state of CA operates the Low Carbon Fuel Standard, which has creating a marketplace for carbon credits (hovering at ~$200/ton now): https://ww3.arb.ca.gov/fuels/lcfs/credit/lrtweeklycreditrepo...

But yes, more is beneficial and will be helpful. We need as many shots on goal as possible!
A true free market requires full information—in this case, that means the ability to determine how trustworthy the "news" being provided by a particular organization is. And there's a big, big difference between an organization that presents genuine facts with a slant (though that can be problematic enough), or one that tries in good faith to provide genuine facts but sometimes fails, either due to bad actors within or simple incompetence, and one that knowingly presents verifiably false information.

"Free market" does not just mean "everyone (with enough money) gets to provide whatever they want, and call it whatever they want, and it's up to ordinary people to figure out what's reliable and what's not."
If you're really split after hours of debate, just agree to surrender the decision to an external authority. Agreed-upon third party or coin flip. Either will do fine.

But really, if you can't agree after a long, honest discussion, maybe the problem isn't with that specific decision. Maybe the real issue at play is a more radical difference of mindset or approach. Sometimes arguments are just really a good indicator that you both need to go your separate ways, no harm no foul.
They were stale, but even freshly purchased ones are often stale. Candy goes stale faster than you'd think, and seasonal candy often sits around longer and is stored with less care than a regular candy bar.
I think this is a bad take, especially saying HTTP is the reason. Its not. The real reason is we want stateless connections and load balancing and because of TLS we want to keep our handshakes warm too.

We also want our retries to work at the application layer too so lower layers would at least have to understand chunks of a connection larger than a packet can fail even if all the packets were acked successfully... _and_ a completely different machine should receive that chunk instead.

We want all that for free and we don't want to pay for hardware. Http/2 is the only close to this and you still need app layer retries.
Other water bridges:
https://www.scoopwhoop.com/Water-Bridges/
Cool!
For the image rendering, could you have a setting to constrain the colours used to currently-available Lego bricks? You might also offer dithering for better image matching.
When you read "government should" that means it's fairly unlikely to happen let alone quick. When you read "government_s_ should" it's next to impossible. Not going to happen. Lee should know better than this. Technological solutions are far more agile and robust then relying on governments all over the world to have a consenses in doing something.
Thanks for this. I still want to try, even if it does fail. Sounds like my idea of a very good time.
Before I touch on Wayland and X, a brief detour.

Let's assume Mozilla finishes servo (their browser in Rust). Let's also assume:

- It's faster than Firefox.

- It's safer than every other browser out there.

How do they get people to use it? Those two are not enough. To the user:

- It's different.

- Firefox feels plenty safe.

This is a real problem and Mozilla faces it now. As a result, they're focusing on what they can do with servo which no browser has done before, like superb VR support. In short, they need features to gain users and they recognize that. Marginal gains are not enough to encourage an entire product switch.

Back to Wayland. Aside from the lack of screen tearing, what can we all agree are big wins for the user? I haven't tried it yet (for this reason), but everything I've read suggests that it could be safer, it could be faster, it could bring some more new features, but mostly it's the same shit.

The masses, and this definitely includes the GNU/Linux using masses, need more than the same shit to change because change is tough. They are going to need something killer from Wayland, or another competitor, before they give up on X.
Businesses always offer you the lowest offer they think you will accept. They can't offer you lower than you will accept, because then you won't accept it ;-) They will never offer you more than they have to just because they didn't pay a recruiter. Don't worry about that stuff, it doesn't factor into decision making.
The US has better housing affordability than pretty much any other developed country:

http://www.numbeo.com/property-investment/rankings.jsp
Both SCA "heavy" fighting and HMB, as in the "Battle of Nations" are full-contact so tend to use armour similar to historical. Very different spins again on the whole topic, but worth looking into.
You're correct, this is a post-processing operation, however I took care to do something that works in real time, so you can use this same algorithm for any FPV transmission, which is the next step that I'm planning to implement (but with more robust features).
Two words: Hippo Bacon
Great article, definitely agree from a buyers prospective. I'm a real estate broker, and am curious to hear if you have the same belief in the service industry?
I remember a Dutch company which tried that, if a certain number of people would buy the would be slightly cheaper. But they couldn't really attract a lot of customers despite a huge budget across Europe. So it failed.
The fishiest part, someone (not verge staff) replied to my comment saying "enjoy your ban".

I wouldn't put too much thought into that. It's probably just someone that knows the unspoken rules better than you do. You see the same sort of flippant "enjoy your ban" posts on neogaf if someone transgresses the unwritten rule of getting within two or three degrees of separation from an unpopular opinion on a hotbutton political issue.
Your definition seems to have its roots tightly coupled to abstraction vs primitive in the sense of Object-oriented programming. Your use of the word "instantiation" makes me feel that way. Let me know if that is misguided.

In the world of concurrency you could probably even call goroutines an abstraction but goroutines are at least closer to the fundamental concurrency primitives such as threads, locks, mutexes and tasks/coroutines/whatever.
China has access to far more information on architecture and technology in general than the US had in 1900, that would shrink the 33 years down a lot farther.
Clearly I was not talking about the normal kind of "infinite loop", but the "malicious" sort.
Protocols and records exist purely for polymorphism. If you want type safety, then perhaps try core.typed:

(defalias Point
(HMap :mandatory {:x Num, :y Num}
:complete? true))

(ann add-vectors [Point Point -> Point])
(defn add-vectors [a b]
{:x (+ (:x a) (:x b))
:y (+ (:y a) (:y b))})
I don't know if I agree with everything that this post says, but I do agree with the bit about two way data-binding being a problem. Two way data-binding definitely gives a "Wow that was easy" impression in a tutorial app or something not too complex, but once you get into the realm of a seriously complex app, it becomes an anti-pattern. You need to know which direction the data is flowing and in many situations there can not be two sources of truth that are always in sync with each other.
I'm working with Ember and I'm really glad that they are moving away from using two way data binding by default.
Removing cars from the city centers would probably also reduce the rates quite noticeable :)
Thanks... Was just about to send out an application today that mentions me quickly winning a contest. Probably there's lots of dumb stuff I'm putting on my applications that I think makes me look good, but is seen as very bad. Wish I had someone who knows these secret factors to run my applications by.

Makes me kind of upset that many employers and investors keep some of their favorite indicators totally secret, except for a few insiders that they share them with.
And we're down again
Interesting that the article mentions his orientation. Seems irrelevant to the premise of the story.
I suggest you check out http://www.altair.com/ they are a leader in FEA tools of all kinds, with offices in many countries. Software development tends to be concentrated in a few countries (depends on the product), but customization of the tools is done world wide. Check out the web site to learn more and look for open positions.
That is what I thought when I decided to give money to Asus with 1215B pre-installed with Linux, I was wrong.
After a quick read of the paper, no. You could adopt this to the GPU (which would require the hashes work on groups of neurons instead of individuals) and might get a similar speedup. Locality sensitive hashing in fact seems like a primitive attention mechanism, with proper attention implementation you could get maybe even better results.
> My solution is that touch interfaces are a bad design in the first place.

Don't get me wrong, I also hate touch interfaces, for all the reasons you mentioned. But saying they're "bad design" is not a solution – it's a starting point at best.

What alternative are you suggesting for smartphone-sized devices? Mobile phones did have physical buttons, but once touchscreen-only devices came out, customers voted with their money. So much so, in fact, that smartphones with a physical keyboard are a tiny niche today. That's because keyboards just don't work well with small devices. Using a CLI with a smartphone keyboard would be an awful experience.
I thought the page was a joke, showing how bad CLIs are.

You think he's being serious?
This is not the solution for every business. Especially a small app that is hard enough to monetize already.
They can certainly lock down future models if they want, but the current models for sale will always be able to boot Linux now. That's a good thing, and even if Apple ships a new laptop next year that only accepts signed OS images from Apple, that doesn't detract from the ability to run Linux on this year's model.
Nothing says “I treat my software seriously” better than paying for its CPU usage from your own pocket.
I am not claiming to be a learnèd man, but I believe that is an acute accent, not a grave accent.
Yes, it does make a lot of stuff much easier. Which is why it is so painful to see IPv6 mired in the mud for year after year.
I am surprised to find this here. I've been practising on and off for the last three years. It's well worth the investment :)
Not quite as aggressive as now. It is called "国进民退".
Validation of Nietzsche's ideas in more of a modern, scientific context. Thinking about a person's morality as originating from a person's psychology.
I would say you have an interesting article here, and your user poll is interesting too. But like you said you don't really have the data to back up this claim, so it just comes off as really click-baity. It worked, as I've never heard of your product and am clicking around the site now, but it's disappointing none the less.
Mosh also refuses to cut a new release, even after almost two and a half years. If you want truecolor, for example, you have to build from source.
One effective way of dealing with a slow bug (or "heisenbug") is to rewrite the system. That sounds crazy, and perhaps it is crazy in a company environment. But when I was first learning to program, I kept introducing heisenbugs once every couple weeks or so. After spending 30 minutes trying to debug it, simply deleting the entire module and rewriting it was unreasonably effective. The total time investment was about 60 minutes.

I haven't encountered a heisenbug in a long time though. Maybe years. I'd like to think heisenbugs are inversely proportional to skill, but maybe it's just luck.
What about others?

I'm fairly certain that Google & al. are no better. That is, they have this massive data trove but have not figured out how to do anything useful with it beyond basic demographic profiling which they still get wrong a lot of the time.

They may have even regressed, or moved away from personal results, because my search results in the past were geared more towards my interests. Supposedly, (physical) location, query, and queries sent right before are the relevant inputs Google uses. Perhaps ads retargeting/tracking also works to some degree.
Agreed. I just got back from the National Air & Space Museum where I saw a few rocket engines, and it occurs to me that somebody had to figure out how to build such an amazing piece of machinery once upon a time, and that somebody was NASA. SpaceX is doing an amazing job, but there's no way in hell they could go from a twinkle in Elon Musk's eye to orbit in 7 years without Apollo, Gemini, Mercury, etc. Even SpaceX's location (El Segundo) was specifically chosen because of its proximity to all the SoCal aerospace contractors.

Great example of government priming the pump.
I don't think circular context menus make a lot of sense for touch based UIs because some part of the menu will always be obscured by your hand. I guess this could be mitigated by having it expand in only one direction based on if the user is right or left handed, but loses a lot of the efficiency of the circular menu.

I like how android does the context menu. Long hold and then a scrolling menu shows up. It obscures the entire screen though, so that's not a model for a larger screen netbook.
I think the alleged appeal of a job listed as being "for rockstars" is a certain amount of automatic respect once you get there. No one wants to go and be some day trader's or insurance adjuster's software lackey, so the idea of being the 'star' of the company is very appealing.

The problem is that this is inherently completely bullshit. Most companies are driven by sales of a service or non-software product, which makes you less important than the people directly responsible for making and selling the product. Even if you're a developer centric company, there are so many 'stars' that there are none, so it's more like being part of the choir that accompanies a rock band (every 10 years or so, when that's cool again). It's pretty nice, but you're certainly going to be held accountable for destroying your hotel room.

In my opinion, the only things that can be appealing about a job listing are technologies used (if they're telling the truth and not just spitting out buzzwords) and location.

On the flip side, if you want me to think your culture is cool and fun (as the 'rockstar' listing aims to do), you have to make sure that every person I meet from your company (or a vast majority) are cool and fun. Otherwise, no amount of buzzwords is going to attract me to your position.
I had no idea about this before this article (I'm not American...) - incredible.

http://en.wikipedia.org/wiki/Japanese_American_internment