HNHacker News
TopNewBestAskShowJobs

mantrax5

386 karma · joined April 29, 2014

submissionscomments
mantrax5··on Justin.tv ending archiving, deleting all archived videos after June 14
Valid points, but you need some strategy for pruning the archive.

We can't just keep everything forever. First it was text files, then html files, then html files with images, and now videos.

Without pruning, the task of archive.org will become impossible, so the question of what's important and what isn't will have to be decided at some point.

mantrax5··on Justin.tv ending archiving, deleting all archived videos after June 14
If you'd re-read my post, you'd notice my focus is on the content's quality, and not its age. Age serves as a useful threshold to review if something should stay or not, but it's not the sole criteria.

Important things will be copied and preserved. That's the natural order of things.

Despite I expressed myself very clearly, I expected two types of reactions: knee-jerk reactions like yours, which argue against something I didn't say; and getting down-modded, because the currently accepted wisdom of HackerNews is that we should hoard any type of information regardless of its merit.

Even though it's explicitly against the rules to down-mod to disagree with someone's opinion, every scoring system gets abused this way eventually. I find this sad.

mantrax5··on Justin.tv ending archiving, deleting all archived videos after June 14
"If the destruction of all this unique user-generated content pisses you off -- and it should"

I'm not sure why it should. When did we get this strange idea that when you make some piece of content, no matter if it's quality or not, it deserves to pollute the cyberspace forever.

I realize this is an unpopular opinion, but one of the reasons nature "works" is that everything old is allowed to dissolve and become the base ground for the new that will come after it.

People naturally copy content that they find interesting. And content which isn't that interesting naturally gets lost. Maybe that lost content stuck around enough to inspire someone to do something in that spirit later or (which also counts), but it doesn't survive itself.

Imagine if everyone gets Glasses one day and starts doing non-stop 1080p video stream of their lives. Are we going to be "pissed off" at that being deleted too?

If you do the stats you'll notice that over 99.99% of the content in archive.org is never accessed. Nobody cares.

And that's how it should be. We should really allow content to die. I have the firm belief that information doesn't just "want" to be free. It also wants to be allowed to die gracefully at some point.

mantrax5··on Pointers Gone Wild
I don't like this spin on humans as imperfect compared to the perfect computers.

Of course humans will make more mistakes, when the immense complexity of the business logic models they deal with surpasses what even the most advanced computer can process today.

Plus, computers also make mistakes. They fail in arbitrary ways, and may produce an arbitrarily wrong result when you least expect it (say, if they overheat).

mantrax5··on Google takes steps to comply with EU's 'right to be forgotten' ruling
What is this thing you call "newspaper"?
mantrax5··on Google takes steps to comply with EU's 'right to be forgotten' ruling
I don't know where you live, but actually yes, you can just change your name.
mantrax5··on The Rise of the $8 Ice Cube
You don't actually believe a product marketing photo matches reality? Any piece of ice will crack as it melts, so it won't look like this. Yes, you can avoid the bubbles, but you can hardly see the bubbles behind the cracks that will form anyway.

Look at a marketing photo of a cheap McDonalds burger, and compare it with the real thing.

mantrax5··on Google takes steps to comply with EU's 'right to be forgotten' ruling
That's kinda useless, isn't it. First, there are hundreds, maybe thousands of "M. Vanger" in any bigger city.

Second, M. Vanger has the right to request that information above hidden as well, so in the end the information would look like:

"M. Vanger, of Hedestad, Sweden, requested that 1 page containing a note of his page removal requests be removed."

mantrax5··on Google takes steps to comply with EU's 'right to be forgotten' ruling
It seems counterproductive to ask every possible data aggregator (of which Google is just one) to allow data to be taken out and hidden from view.

If John Doe has something so embarrassing in their past that would warrant this, it can be accomplished by him changing his name.

I mean purely speaking as engineer, I'd make the central reference (the name) invalid, and not go check every possible reference user.

mantrax5··on Scalable, Robust and Standard Java Web Services with Fibers
I'm highly interested in all of this, but I can't understand a damn thing from the article.

How does Quasar implement fibers? How is code transformed to CSP (is it at all?) Where are the yielding points, etc?

mantrax5··on How Apple Cheats
Apple has no dominant position in smartphones, so you may at best argue they have a dominant position specifically in their own iPhones.... But if Apple making design decisions for their iPhone product line constitutes an "abuse of dominant position" where do we draw the line exactly?

- Should Apple be forced to open all internal APIs to third party developers?

- Should Apple be offering iPhones with alternative operating systems?

- Should there be an open standard so people can build compatible iPhone clones?

No. iPhone is Apple's product, and they decide how far they will go in opening up their platform.

Third party developers are not fully trusted to do the right thing, and as you can see with Android's malware situation, it's a good thing Apple is not letting random developers do whatever they want.

Since Apple is held responsible by both developers and users to have a reliable product, when they decide to make an API public this is a huge commitment.

Apple has to guarantee said API will be supported in a reasonable way in future OS releases, it has to guarantee to users that calling said API won't result in poor UX or security vulnerabilities.

The situation is much different for Apple's own apps, as Apple can then make the personal guarantee it won't be abusing its own APIs to create poor UX and implement malware.

mantrax5··on How Apple Cheats
You can't download executable code to an iPhone app outside the App Store, only data.
mantrax5··on How Apple Cheats
Oh yeah. Without UIPopoverController on iPhone, it's like you lease your phone, and at any moment Apple may pull the string to that UIPopoverController and take their phone back.

Do you even read what you write or you just mash the keyboard and hit "reply"?

mantrax5··on How Apple Cheats
I like how your rant about "trying to tie people into their ecosystem" has absolutely nothing with the situation here, which is the fact Apple's apps use some harmless private APIs before they finalize them to a degree to make them public.

Tell me, what other "expected and only logical" things did you encounter while reading the article? I'm sure there's an alien invasion conspiracy theory in there somewhere.

mantrax5··on Goodbye Google Code, I'm moving to GitHub
There's this notion that because a service is free, the provider shouldn't give a fuck about the service they're providing, and the user better be thankful the service exists at all.

There's also this notion that if someone provides a service, even though it's free, they obviously have some business model or similar interest or they wouldn't do it, so they better give a fuck about their users, or their users are gonna hurt them as a provider by leaving for another provider.

I won't say which is right and which is wrong (I feel both are wrong), but the two are obviously in conflict. The whole open source community is based upon the former. Ad supported data-mining businesses are based upon the latter. Hence the conjecture by the OP.

mantrax5··on Check your Google history
I don't advocate deleting the history of my clients, do you have problem with reading comprehension?

The thing I "advocate" happens to be the best practice recommended by Google (if you'd care to dig into the docs, and no one does) for sharing the administration and viewing of Site Analytics groups (they're called Site Analytics "accounts" which are inside Google "accounts" so you can imagine that many folks get confused over what is what).

The best practice is not to create a new Google account and not to share that account's password with strangers (or even friends). There's a method for sharing just analytics with other Google Accounts, buried in the Site Analytics admin panel.

With that setup, the client will be creating a Site Analytics account within his personal Google account, and sharing said Site Analytics with my personal account. And I won't be able to see, let alone delete or disable their search history. Alas, that's not how things usually go.

People just don't get it, so they create new Google accounts over my head, share it with everyone, and everyone's search history ends up in the shared accounts. So when that accounts gets to me, I delete & disable search history. I know for a fact no one who ever logged into this shared account intended to share their browsing history with people.

Exacerbating the problem is the fact Google accounts are intentionally designed so that you log in and forget you're logged in. Google wants to know who you are. The accounts are also designed so that if you want a standalone account for analytics, it's a full-blown Google account, so you end up with people's search history in there (and a bunch of other services no one asked about, like email, docs etc.). And people don't understand the implications of sharing a Google account they've been logged into.

By the way, thanks for twisting my words and intent out of shape like you did. Now that I've had to waste the time to explain my original post as if to an imbecile, I'm sure everyone reading this will gain clarity about the situation I was describing. Cheers.

mantrax5··on You shouldn’t use a spreadsheet for important work
We've done business with pen and paper for thousands of years.

I think we can handle spreadsheets. While I'm a programmer and often find it easy to whip up a program to do what many would do in a spreadsheet, I don't have the arrogance to tell people to not use spreadsheets for serious work.

On the contrary, I encourage it. It's a wonderful tool, and, in the end, superior to pen and paper.

mantrax5··on Hacker culture and the fear of wysiwyg
For as long as I remember IDEs have had said drag-and-drop interfaces, usually centered around the coding of GUIs, and no one has said that just because an IDE has a visual form editor it's not programming.

You're the one making up the distinction and arguing against it.

The primary reason that not everything has turned into a drag-and-drop interface is that it's highly inefficient. It remains a fact that compared to manually hunting for class Socket in tab bars and scrollable lists, just so I can drag it and drop it somewhere, it's far easier to just use your keyboard and type "new Socket" in your code, especially with autocompletion at your service.

mantrax5··on Hacker culture and the fear of wysiwyg
Why yes, we're not stuck with 80x25 green on black terminals.

Why even mention it? By the way that nested hierarchical tree is also written in text (HTML and CSS). So is the hyperlink. URLs? Text.

Check any modern IDE and you'll see similar visualizations over text based source code. I can explore my project in a tree-based outline in my IDE. I can open my classes as an UML diagram.

Turns out we're already in the future. Celebrate?

mantrax5··on The "Work For Hire" Doctrine Almost Never Works in Software Contracts
This is like arguing with a religious fanatic, to be honest. I don't think you'll ever get it.
mantrax5··on Check your Google history
An account specifically created to host a site analytics group, and which clients always accidentally remain logged into.

I think I'll get above your cheap outrage and say I did the right thing by going in and disabling the search history.

mantrax5··on Check your Google history
If anything, it'll improve your searches. I always disable search history, on all my accounts.
mantrax5··on Check your Google history
So I always tell my clients to not create new Google accounts just for their site analytics, because Google tracks all kinds of shit in there.

But they don't get it. So when they inevitably give me that account, I go and delete and disable the search history.

But let me tell you. To disable the search history I first need to open that page, and I've seen a bunch of searches I honestly wish I wouldn't have.

mantrax5··on The "Work For Hire" Doctrine Almost Never Works in Software Contracts
Yeah. Copying software is free, dude.

1. Fuck supporting your software though, your time is not free. If people keep calling and asking questions, fuck 'em.

2. Fuck dealing with the resulting fragmentation from people forking it left and right. This would incur a very serious damage to your client as well, but fuck him too.

3. Fuck maintaining your software. Because the configurations and platforms people will be deploying your software to are nothing like the the ones your client is paying you for, so the bugs your client sees and your open source users see are nothing alike.

The point I'm driving, is that it's easy to talk about how copying code is easy. But your code is worthless without considering everything else I said above. And all I said above requires your involvement, your effort and your time.

I mean people are easy to copy too. Practically free. But for some reason, sleeping around and abandoning your children afterwards is not considered a noble act.

mantrax5··on Hacker culture and the fear of wysiwyg
It's been the case for decades.

Literally before PARC had their Alto nailed down, there have been visual programming languages where you draw and connect boxes in order to program.

And you should think really hard why (for the most part) we don't program this way today. It's not because we're just stubborn.

BTW, there are actual flying cars too.

mantrax5··on Hacker culture and the fear of wysiwyg
Let's continue with that approach.

Then maybe hitting a letter should only render the letter at the same size and font as the one printed on the keyboard.

And if you want to change the font, well it's just a drawing, so you can't. It would make the keyboard non-WYSIWYG.

mantrax5··on Hacker culture and the fear of wysiwyg
The seeds have been "everywhere in the last couple of years" for decades now.

It's the programmer version of "flying cars are coming".

mantrax5··on Hacker culture and the fear of wysiwyg
> I believe, contrary to almost all programmers, that this is in fact fundamentally a cultural problem, as the author points, out, and NOT a practical or technical problem. I think the problem is more fundamental than the author suggests though.

Prove it to me by explaining your complete point without text, in pictures.

On a more serious note, we use text to represent symbols, because symbolic coding is powerful and pretty much the basis of our civilization, long before computers existed.

Text is powerful enough that I can talk about "Mercedes S-Class car" by hitting a few buttons, instead of spending the rest of my day drawing a Mercedes for you.

Symbolic coding can be expressed via graphics too, but it remains symbolic. Say, I could draw the logo of Mercedes, then draw a symbol resembling a car, and I wouldn't have to draw an actual Mercedes car for you, but what's the benefit compared to typing it? It's again the same, only much less efficient. Egyptians used to do it like this, but they've since changed their mind about it.

If you'd represent a program as a visual graph of function calls this is still not WYSIWYG, it's just another set of symbols representing the same abstraction. When you run the program, what you "get" isn't a graph of function calls, it's something else entirely.

So it comes down to what is more flexible than text for representing symbols, and honestly I'd like to see anything better than text.

It's not just source code which is based on text. We're communicating right now via text.

The web is build on text ("hypertext"). Web search is based on text.

Look around yourself. The majority of communication is symbols, and most of it is text.

mantrax5··on A New “Theory of Everything”: Reality Emerges from Cosmic Copyright Law
Yes that's what it implies. There's a privileged truth and we don't get to know it. Don't feel bad, though.

You can describe the laws of physics like little gremlins who follow a book of laws that happens to be the laws we know, and the predictions and observations we have will match the gremlins theory.

It doesn't make the existence of tiny gremlins real.

mantrax5··on Hacker culture and the fear of wysiwyg
Uhmm.

Ok, let's say you're Tour de France competitor, and you're told to use this:

http://www.christydena.com/blog/wp-content/uploads/2010/02/t...

Is "fear" the correct word for your reaction?

WYSIWYG is a good thing in predominantly visual programs (photo editing, vector illustrations, animation tools).

WYSIWYG becomes a problem when the content being entered has semantics without explicit visual cues. By definition you can't have a "WYSIWYG" for semantical information, and if you give people a WYSIWYG HTML editor to enter content, they'll just tweak the code until it "looks" right, which will bomb when said content has to be transferred to a new medium (say, non-HTML).

People may be liking Word, but the majority don't use it semantically, they just mash the font settings until the document looks approximately correct, never mind the document outline is a mess, because half their headlines are not headlines, but paragraphs with enlarged text.

← PreviousPage 4 of 8Next →