skysight-inc/HackerNews huggingface dataset:
I started developing network apps before REST existed -- probably like many people here, that wasn't long ago, SOAP, various things like RMI and then XMLRPC were things. SOAP was never good anyway, deeply buried in standards committee goo. But there are still things I miss from these things. When I found XMLRPC after doing all these things, it was very much a "WOW" moment. (JSON of course, with it's definite differences between maps/hash-tables and lists, is greatly superior to me).

A generic problem with REST APIs is they all handle collections, associating items with subcollections (including establishing and removing 1-to-many or many-to-many relationships between existing objects), query strings, authentication, and pagination very very differently.
Not all APIs are discoverable either, many don't do structured error codes. Thus to talk to one, rather than just using client-library, more work has to be done, often repeated work in multiple languages. Lots of REST APIs aren't well discoverable and rely on special logic to form up URLs, and many have weird verb pollutions - modelling a long running job for instance, I've typically have done as posting a job descriptor to a job collection, because the standard verbs don't really apply.

All being said, I prefer a nice broweseable REST API, but despite the accursed "XML" in the name, XMLRPC was easy - there were bindings in multiple languages and it was easy to ask an API what methods were supported. Problems came in the undefined parts - like whether "None" could be passed, and so on.

I can design and build some very elegant REST APIs, but the clients DO have work to do, every time. A good example for me was trying to write to GitHub's API, and then being angry at the way pagination was overcomplicated and URLs were not discoverable. (It might have gotten better).

BTW, if you are doing Python and want a GREAT foundation in pagination, discoverability, and so on, I recommend Django REST framework. One catch is you may wish to extend some of the serializers to return URLs relative to other URLs.

I don't think RPC is evil so much - over HTTPS and backed by a good webserver, and done so that it's stateless (something a pre-forking webserver (esp with MaxRequestsPerChild in play in Apache) forces you into, not so much REST protocols all by itself), I think it's just not socially acceptable.

So statelessness good, having to write client-specific "flavors" of REST, well, it's just reality.

(In other news, I'm disappointed all my He-Man figures got sold in the 80s so I can't illustrate tech cartoons with them, well done)
I'm sorry that our pricing page is not easy to find! we have got tons of complaints! we are working on it! It's actually $10/Month unlimited contributors and up to 10 blogs (sunsed.com/pricing)

Please try our editor with the 14-day free-trial (no credit card required).

We are also working on putting our editor on our homepage sunsed.com so people can try it out without signing up!

I'll do everything I can to gain your trust and business!

Thanks for your feedback!

@seyedip
The character's name was actually Cypher. Not sure if the Matrix reference was a mistake or if I'm not catching onto something else.
They used to call it "paying your dues". The fact is some of them will be exploited and get nothing, some of them will make a huge name for themselves and learn how to build businesses instead of following a traditional career path.

Personally if I had it to do over I would take my chances at being exploited in SV over the career prospects of doing things by the book in middle America; and fwiw I'm saying this as a college-educated late-comer to Silicon Valley (8 years ago at 28).
Faster 10-bit video conversions in FFmpeg
I have been where you are.

Constantly gauging the aging people around me, anecdotally trying to gain evidence as to what makes the longer-lived live longer.

Understand a few things:

1. It's natural to fear death
2. Fear is a motivator to protect us
3. We can't protect ourselves from the inevitable
4. Everyone who lives will experience death

Because of these three things, we can start to understand that our anxiety about death, while well-intentioned, can become irrational. We convince ourselves that we have the power to prevent death, because we have the power to prevent or treat many diseases. In this way, death is treated as unnatural. We see death as the end of consciousness, and we fear it because of our instinct.

I, like AnimalMuppet and others on this thread, am a religious person (Christian with some extensively explored views on deism, Calvanism, etc). This gives me a sense of hope, that consciousness and being have meaning beyond my seemingly short life.

Our brains are tricky things. We convince ourselves of non-truths often. Understanding that our brains are not our "selves", that indeed we can view the brain as a part of the whole, we can begin to externalize the strange occurrences in our brains and study them more objectively.

This objective study of the mind helps us separate our "self" from the body altogether. For me, this is my true identity and spirit, that feel altogether out of place in a frail body.

Consider meditation. Certainly get exercise; it will help you become healthier, and reduce anxiety (proven in study after study). Accept inevitabilities, and focus on the moment you are in now.

If you would like to talk more about faith and religion, I and I'm certain others on this thread would be happy to discuss it with you!
It would be a good idea to provide access to that sort of equipment on the ground. Bugs that can lead to loss of life should be of much higher priority than bugs that can merely lead to loss of profit on a web site.

Though the avionics industry would obviously balk at the proposition, those systems are already spectacularly vulnerable, and they'd hate to lose face.
Thank you for your suggestion! We are actually thinking about it!
I think it's the intent and commitment that defines it. Someone who does not, as a rule, consume meat or animal products is vegeterian. I think that's true if they do it for one day or a thousand, and IMO it's also true if they occasionally consume an animal product due to necessity or ignorance or mislabeling.

By contrast, ~80% of my food intake right now is Soylent. I could make that 100% if I wanted, and I suppose that would qualify me as vegeterian; Soylent contains no animal byproducts. But I don't consider myself vegeterian and never will.

Edit: I tend to look at this like a religion. Can someone be Christian if they aren't in church every time the door is open? Do they have to follow every rule and think correctly and so forth 100% of the time? I think most people would say no.
> taking the PC from a geeky hobby item

That was Apple. Microsoft mostly copied things after they got proven elsewhere first.

How many hundreds of billions of dollars have been lost to security issues in Windows? The design is fundamentally flawed and entrenched in our society for the foreseeable future (ATMs running 20 year old versions of Windows, etc).

How many other promising computer futures could we have had without abusive monopoly power? Plan9? Be?

How many millions of programmer hours have been lost to supporting broken Microsoft practices? IE, anybody? It didn't just "happen," it was their entire business model: destroy competition by abusing a position of power, become the only solution provider going forward, then stop developing the solution for highest ROI (just duplicate those bits for government contract money, baby. no need to maintain anything since we're the only game in town).
I suppose if you have boat loads of cash to burn, a couple thousand a month would not be a big deal. For a bootstrapped startup, money is a concern.
Aurelia adopts ZenHub.io to improve communication with developer community
But REST is RPC. I've read the article and the author basically defines RPC as a HTTP API that doesn't use the HTTP methods in a semantically correct manner but that's not what RPC is. RPC is any remote procedure call. It doesn't even have to be HTTP-based. Message queues are an example of something that's not RPC.
I think there's something odd about our society if suddenly we are all deathly afraid of chairs.

It should be lions. We need to reintroduce lions into our suburbs.

What? Your suburbs didn't originally have lions? More reason to add them then.
I have a feeling, you have not seen death from close quarters. Once you have seen it up close, you kinda of get used to it. Also it is little unusual to think so much about death at such an young age and these may be signs of spiritual inclinations. And you could consider surfing few books (Buddhism, Zen Koans etc).
A house in Houston being sold for for $150.00 and an essay
I actually prefer RPC. It's not very often I'm making a call to a server that I don't want to have complex logic behind. The REST paradigm doesn't fit that (though you can wedge it in).

REST GETs are fine for getters, and I generally like REST URLs because their prettier and don't have god-function smell like you get with SOAP.

But for commands, a POST with params to distinct URLs for each command works fine.
A little bit general but I got the

Toshiba CB30-B-104 13-Inch Chromebook (which your link suggests). :)

Thank you.
If you have a 1:1:1 relationship between database models, in-memory models and the REST endpoint, and the primary purpose of the API is to manipulate these entities, there's a reasonably strong stylistic benefit to REST style. Not all applications are like this, but many bread and butter CRUD apps are.
That looks good but a little bit pricey for what it is to me. Especially as I actively avoid touch screens. Thank you however, it does look like a good laptop.

In the end I got the:

Toshiba CB30-B-104 13-Inch Chromebook
I'll check that! thanks!
We've been working on a way to provider similar users to you based on how you rate, creating a unique 'people like you' average movie rating. Feedback welcome :)
they need 2666 applications to hit the appraised value. Think they can?
You are awesome! we are discussing it... :)
Performance is an interesting way to differentiate your product from other platforms, though I'm not sure what kind of value high performance offers in this space.

I don't think you're selling it well. Performance comparisons to other platforms with clean and rapidly-digestible charts would really help convey what makes your platform different than others when it comes to performance. I have no idea, for example, whether "5ms page creation time" is good relative to other platforms, nor why I should care overly that other platforms do the same in 10, 15 or even 100 milliseconds. Convince me that I should!

The speed at which the menu slides in does seem antithetical to selling 'fast', if I'm honest. It reveals itself too slowly. If speed is an important attribute of your product, everything should be fast!

I like — really like — that you have usably-fast live search. That's a great headline feature, and something few other platforms do! Along with the editor, I think these two features can make your platform stand out in a meaningful and valuable way.

I think leveraging Disqus as your social story is probably a reasonable decision, but I think there's room for evolution there. Rolling your own solution — something that really creates a network for SunSed users — may be a longterm goal, and may help you meet/exceed performance expectations.
I'd say this is close, with a slight twist.

Insisting on a formal definition that would work across contexts is harmful. If someone comes up with one, that's nice (I doubt this). But even then, others might come up with "type systems" that fall outside of this definition and that's still perfectly fine.

The twist is that we do not need formal definition to talk about types across multiple contexts. I do not know what the best way to do this is, but the essay has some suggestions inspired by philosophy, which might be interesting precisely because they do not need clear formal definition.
I've enabled VoiceOver for testing but had not seen that gesture, thanks for the pointer. It is useful but slightly awkward as you need both fingers to retain contact with the screen while rotating, which is challenging for a 360 degree rotation :)
It's 2015 and Winamp is still the only music player that really whips the llamas ass.
Amazon Echo is finally becoming your shopping assistant
I prefer REST for mainly aesthetic reasons: the URLs are pretty, and in Rails I can handle different HTTP actions in the same method, which usually ends up being some clean code:

def index
if request.put?
update_stuff
end
# get/put render same response content
end

One of the unexpected benefits of intercooler.js has been that I can use REST-fully designed end points for my html-partial endpoints, and it all just "looks right", even though it isn't a traditional JSON API.
One point that didn't get addressed in this article is the use of HTTP status codes to indicate the result of a request. REST encourages proper use of status codes – 404 for a missing resource, 422 for invalid data, 201 for successful resource creation, etc. – further enhancing the predictability of the API. How does RPC handle status codes?
If nothing else, your anonymous prediction pleased the author :-). Thank you!
Exactly what you'd expect from an airline:

"Bugs or potential Bugs you discover may not at any time be disclosed publicly or to a third-party. Doing so will disqualify you from receiving award miles."

It's as if it was designed in the same spirit as a frequent flyer program -- really stingy payout, with lots of strings attached. I can't see how this can incentivise anyone to do free penetration-testing for them.
With a POST. The parent just pointed out that GET should not be used for updates. They didn't say that only GET should be used for retrievals.
Just to be clear, what we're doing is helping our customers uncover issues in their vision for a feature or product before any code is written. This means that our Reviewers actually assess requirements. By finding the weaknesses in the requirements early in the process, we can enable Product Owners, Business Analysts and Product Managers to craft more complete, more accurate requirements. We've been working so hard on our platform! We hope you'll join us as we work to free the world from poor quality software!
I agree with you (overall).

Somewhat sad that you pulled sports into the equation as a part of the negative persona. Also, kind of ironic that you didn't pay attention to the sports event they invited you to. :)

(End sportsball shaming!)
> If a user want to stop using your service, you’ll do this (not so obvious) call:

> DELETE /users/1234

No! It would be

DELETE /sessions/12345

or possibly

DELETE /users/1234/session

or even

DELETE /users/1234/sessions/3

in the case a user can have more than one concurrent different sessions (this is actually a fairly common case for the application we do were I work. We don't use http for this though).

Unless you actually want to permanently stop the user from using the system, in which case

DELETE /users/1234

would be the perfectly obvious choice.
My guess is wifi and entertainment are excluded because United doesn't build those. Depending on the aircraft they're provided by Panasonic, LiveTV, etc. in the case of LiveTV (United's vendor for DirecTV) it's even seller-financed.

United probably isn't interested in paying for someone else's bugs.
Lasting progress for the very poor: Evidence from six countries
And, a farcically low payout for otherwise very expensive consulting work from highly skilled people.
Reddit Enacts Anti-Harassment Policy After User Complaints
It would take a bit more than using a hard disk rather than an SSD to create a 3 minute load time. It must be downloading the entire program over the internet every time.
Amazon is not super keen on people pentesting from or against their infrastructure.

You will be better using labs available as ISO or VM.
I'm curious about your decision to go with curated.co instead of something like tinyletter.com. Just simple stuff like bringing your own domain?
I spent ages looking and looking at this question around human-readable serialization syntax and whether a substantially better syntax is achievable.

I concluded these things:

* The structural forms that readily come to mind(linear, hierarchical, graph, relational) all have some kind of existing representation, or an easily achieved bootstrapping. They are all Good Enough at the basic problem of generically encoding the structure.

* What keeps us tied to existing formats like XML or JSON are the data types they can encode and the bidirectionality(i.e. a serialization and unserialization loop will leave the data unchanged). For moving around raw data in a textual form, these are difficult to beat, although efforts like SML may succeed in eking out a slightly more terse form.

* If we only make the syntax more forgiving, edge cases appear where syntax fails to encode some data. If we add special case syntax to encode that data clearly, bidirectionality becomes problematic and risks making everything unreadable. Correcting for these cases leads us back to the starting point of mediocrity.

* Substantial improvements for human editing come from moving away from a generic solution towards a source-format schema targeted around the domain problem. This allows the parsing to relax its requirements and simply fail with bad source data. Automated editing of these formats can also maintain the source as it was entered, because it's no longer bound by the requirement of being computer-centric - it's only manipulating the key symbols in a limited way, in the same way that we manipulate strings without fully knowing what the strings mean. The final meanings are obtained through a separate compilation process.
The Continental website isn't pretty but it's very functional. Old United's site was called united.bomb for a reason.
A missing factor is fragility in the face of change.

RPC leads to fragile protocols. Adding arguments to a procedure or adding properties to a result can often break clients and in practice you update systems lock step.

HTTP can gracefully handle different API version requests to the same resource. REST clients are encouraged to take only what they need from the representation.

Also, I strongly disagree with the Totaling points section. Seems too "nice" to both sides.
I worked in the Cosmic Ray Research group at Utah as an undergrad and postgrad. I started at the tail end of HiRes, which was the sucessor to Fly's Eye, and helped develop, test, deploy, run etc... parts of the Telescope Array experiment.

I know a bunch about these experiments if anybody is curious.

Also, AFAIK, Telescope Array has the only approved outdoor LINAC^H^H^H^H^H "electron light source" they fire directly into the sky. We joked about it giving birds cancer. It's also a potentially an awesome lightning rod.
Sorry... I want to make sure I have this right. Is your argument that exceptions would a better idea really that the version with sum types doesn't let you get away with the common antipattern of checking for file existence before opening it? Because what you should actually do in that situation (not, I stress, just in Rust, but in any language!) is just try to open the file, which makes the check-and-open operation atomic and results in a single error call. In other words, this is an example of how the Result type guides you towards the correct solution--which is pretty much the strongest reason I can think of for including a feature in a language.
I really like the approach that Spotify take to working on new features, the squads idea is quite good. I think it is important that people occasionally break out of their cliques and work with new people, I have found based on personal experience that working with the same people day-in-day-out will eventually give you tunnel vision. You stop learning from those around you, eventually the hive-mind becomes one and there is little free-thinking. Breaking out and working with another squad I think could be beneficial to Spotify.

This is where the praise ends. As a Spotify Premium user, I love the service, but the interface as many others have pointed out has really gone downhill. I don't know who is leading the UX squad over at Spotify, but the app needs considerable work. High startup times, incredible amounts of frame rate lag and removal of the system tray icon. What is going on over there? I have also noticed that the app can play a song quickly, but browsing and searching is incredibly slow (even on a fast connection).
I like how when building REST API servers and clients there are standard components that just works. The entire API in the same format means it is easy to write a DSL across the entire API configure each endpoint - such as row level and field level permissions, pagination, filtering. If you have a well designed RPC you have the same benefit, but except with REST - you can reuse someone else's work because the design is the same. It literally takes 20 seconds to change the /user/ endpoint so:

1. Non-authenticated users can create users, and see a list of users with details that are public.

2. Authenticated users can view their own public and private details and have read/write access to most fields except is_staff.

3. Staff users have full permissions for users that belong to the country they are managing.

4. Superusers have access to everything.

Without the benefit of DSLs this would take hours to write all the if/else statements and unit test them. It would be a nightmare to do the same for all your endpoints. I assume you can write some abstraction functions to use for all your RPC endpoints but it'd be easier to reuse a library from past projects that had the same REST API design.

Example:

Row level:

permission_classes = [
Or(And(Or(IsOwner('id'), IsStaff), IsUpdateOnly),
And(AllowAny, IsReadOnly),
And(AllowAny, IsCreateOnly))]

Field level:

is_public = And(IsActive, Is('is_public', True))
fields = {
'display_name': [],
('is_active', 'password', 'email'): [
Or(is_staff_or_owner, IsCreateOnly)
],
('full_name', 'slug',): [
Or(is_staff_or_owner, is_public, IsCreateOnly)
]
}
Imagineer – Handling 404s and Generating Images Using AWS Lambda
Yeah this probably will end with someone either being arrested or sued. They'll either a) raise more than what they want for the house (incredibly unlikely) or b) "award" the house to a related party and never leave.

Also if you scroll to the end of the site, you see "Not what you're looking for? My name is Michael Wachs and I'm a Realtor®. I'd love to help you with anything you might need." So maybe he's just trying to get exposure.
That is true, but I like to believe that if a group can solve a whole class of problems with a new language, that means they can spend more time and effort on other types of security problems.
Before Aurelia adopted Zenhub, I had never heard of them before to be honest. A brilliant idea putting an interface over the top of Github issues, this is one of the things I have been wishing Github would implement themselves for as long as I can remember. It makes seeing what the status of what is without needing to paginate through a hard to read list.
All pen testing labs I have seen are VMs
Australian data retention regime already expanding