samholmes

Really? No comments? Has AI completely shot down excitement for real devs who “use vim btw”?

I'm excited about this idea. I don't like using non-open source thing because I like to know that I'm investing in something which I can tweak and contribute to. Open source is all around a better idea.

I also like the idea of using on-prem models. As open source LLMs get better and hardware gets cheaper, I can see being able to use local models being the winning advantage.

Please give me early access!

Account creation process is unnecessary. Biggest issue with the app

I had a feeling it was going to be mentioned that I need to delegate the marketing a partner. Does this mean that for anything to be successful one must need a partner to complete the other half (or be superman and be good at both)?

Why would I want to run Android apps on any device?

What does this have to do with hacking?

I guess I could live on that amount. :\

It's not so smooth for me. :(

I've updated some things to this design.

* I made the background not white, which seemed to be hard on the eyes; I decided to keep the color scheme from orignal HN.

* Changed vote button icon; moved point count together with the button.

* Moved comments from the right to the left, closer to the link and vote button. Reason: it's too important of an element to have it be all on the very far right.

* Moved less important content (time and poster) to the far right.

* Internal stuff: I'm using localStorage APIs to cache the data I'm scrapping from a third party hackernews API source. This is because the source kept getting hiccups.

Here are my questions to the rest of those who are still interested in this endeavor:

Should I go with grey text on white, or black text on tanish grey (like it is now)?

Are the icons too distracting? Are they good, or would you suggest I do something else? Maybe I should ditch the orange background on these icons, and go with orange text when mousing over the buttons?

Some idea I have planned:

* Search field in header * Automatic next page loading with ---page n--- separators (if I can get this to work with the API I'm using) * Replace submit button with a visually persistent composer item.

Let me know what you think of these ideas too.

What sort of malicious things can be accomplished with a cookie tossing attack?

It's slower because it hooks into an unofficial API. YCHN has no API I can use, so I had to use what some other sites were able to scrap.

True. I need a good API to hook into in order for it to be functional. Maybe that could be another project, if anyone wants to help with that. :)

This is a continuation of a post I made a couple days ago, title "Hacker News Redesign". It was a link to a jsbin. This time, it's a Github Page, which means it can update, so check back often.

I plan on accepting feedback on this redesign. I already took some feedback from the last post. This time, I can update the project upon feedback, and keep a dialog about the design.

Hope you enjoy it! :)

I'm going to design this thing into a Github page, but I need to get HN feed data. Could someone comment on where I could get HN data through an API?

I want to remove the metadata if I can. Would you agree that the titles and "comhead" (the domain name) should be the visually promenant part? My goal is to minimize on the meta as much as possible without removing the usefulness of it.

There will be less white space and it will be used more scarcely, however I'd rather use a little bit of white space instead of something like a horizontal line. Wouldn't you agree with this? :P

I agree. My intention is to use white space to separate things, vs lines or other graphical distractions. Having said that, I still need to work on the list part of the design.

Wow! I really didn't expect this much attention and feedback! First, I want to say thanks for all the comments!

I designed this last, late California night. So the design isn't finished; this is a first draft.

Obviously the posts themselves are an issue. I didn't put much attention to the posts. I'll do that. Some of the feedback I got on it were: 1. Larger vote buttons. 2. Less contrast (too hard on the eyes). 3. Too much white space, a little too small of text. 4. Focus on title, not author.

Some other feedback I got was on the orange color. I pulled this straight from HN's header bar. I guess because the bar is taller that the color is brighter. I need to think about if it's the color or the surrounding elements that make it feel this way.

Keep up the commenting and feedback. I'm not finished here yet. I really liked the HackerWeb design, but it's too narrow; it feels like a mobile app. I'll pull some inspiration from there, but I really want to bring the design back to a "hacker" feel. So stay tooned!

I designed a slightly new Hacker News. Comment and let me know what you think.

Looks like I should be selling pizza

The purpose of the post was to re-define existing terminologies. I've researched into Elm, and I like that they called these "behaviors" signals instead. And instead of FRP (which honestly sounds like a fart if you pronounce it), I wanted to coin SOP and compare it to OOP, in that it could be a term used as a foundation for a new way of programming.

I wanted to compare signals to that of event emitters, and show how they're each like a single event. This will hopefully help to make others familiar with the applications of signals.

I think FRP, or SOP, is brilliant and should be implemented in JavaScript. There isn't any non-benefits to having signals in a language, especially one that's so heavily dependent on events and functions like JS.

Looks like this concept is out there. FRP (Functional reactive programming), or as I like to call it FAP (functional adaptive programming ;P), is the idea that values (return values even) can change over time and therefore all statements depending on those values will re-evaluate. I like this concept. It's almost like all values can be streams of values. I like how Elm (programming language/DSL) calls them signals because they're almost like streams, but hold a value at any given time (I suppose). I really wish JS had this implementation.

Updated the entry with some further examples. You can see how this makes libraries like async (by caolan) unnecessary. Asynchronous functions could just be functions that don't return a value immediately. Other statements that depend on these values being returned by the asynchronous functions would be queued for execution automatically by the interpreter. This makes all async parallel, and async in a series wouldn't even be in the thinking of the programmer.

This is true indeed.

Anyone have any more information on this?

WebOS could do something different and allow for apps to be loaded on the fly via a URL. Oh wait, that's what a web browser does..Why isn't WebOS aiming to be a web browser with the ability to cache apps using standardized (or maybe non-standard if needed) technologies? Then, you wouldn't need a marketplace or app store necessarily, because users have access to the apps directly off the web. Not to mention, this will save storage and move towards cloud computing more nicely. Oh, and think about how easy it would be to transfer an application from device to another device. WebOS should focus on being just that, a web OS. This means URLs; DNS is the backbone of the web after all.

Is this storage method only good for read-only data, or can it survive multiple re-writes?