vasilakisfil

Joined 12 years ago

Karma
333
Submissions
134
Member since
Sep 11
View on Hacker News

Recent submissions

Comment · 4 years ago
you are right, not so useful for Result type, but still, it comes handy for Option types (since None doesn't hold anything).
Comment · 4 years ago
I skimmed through their docs but couldn't find whether they:

* support for abstract apps, not only HTTP/web apps like heroku, let's say I want to deploy a SIP app

* support for HTTP/2 and potentially HTTP/3

If they do support these two I would say it's enough to be considered Heroku killer.

Comment · 4 years ago
it's so funny how everytime services are down, their status page is like everything is normal here. I understand that there are internal politics around such things but still...
Comment · 4 years ago
I wish I could use one of those, I had one actually some years ago but my eyes were burning (I have huge fonts compared to average people in my regular 17inch laptop).
Comment · 4 years ago
Usually you need redis to scale up horizontally, meaning with multiple servers/processes, and still keep consistency in your data. In general redis is a very useful tool that provides various features, even pub sub.
Comment · 4 years ago
> Returning a 2xx code immediately tells the client that the HTTP response contains a payload that they can parse to determine the outcome of the business/domain request.

There is nothing in the protocol that mandates only 2xx status codes are parsable. Instead, the Content-Type pinpoints to the client what kind of content the body has, regardless the status code. And the content-type will most probably be what the client asked (if not, then the server announces that the response content is not subject to negotiation, something that you see rarely nowadays..)

In general I think this post reflects one of the mentalities that appeared around 10 years ago regarding HTTP APIs (another was the extreme hypermedia-driven APIs). But I really think nowadays we can do much better, we can deliver a practical API that works 99% of the times.

By the way in the latest HTTP RFC (RFC9110) status code 422 is finally officially defined (previously was part of webdav extention), which means that the war 422 vs 400 for validation and other semantic errors is over and we have a clear winner. But 200 vs 404 for something that was not found? Well that was has ended long ago I think..

Comment · 4 years ago
Serialization/deserialization is such an important part of web development, I have no idea why Rails includes the ancient JBuilder (and very slow since it goes through templating) library, instead of investing in a proper library. Let alone deserializing which is equally important..

I think the API Shale provides is pretty sane. I would probably use it in my next Ruby/Rails project. I don't like the fact that Nokogiri is included by default, it would be nice to declare a core type, and then bring in what you need (JSON, XML, YAML) as a different gem. But that's not a deal breaker for me.

I have created my own serializers in the past (SimpleAMS[1]) because I really detested AMS, no offence to AMS contributors, but AMS library should just die. Rails, and way more importantly Ruby, should come up with an "official" serializers/deserializers library that is flexible enough, rock solid and fast. For instance I had done some benchmarking among common serializer libraries [2] and AMS was crazy slow, without providing much flexibility, really (meaning, slowness is not justified). Others were faster, but were supporting only one JSON spec format (like jsonapi-rb). I am wondering where shale stands.

Another thing is that most serialization libraries seem to have ActiveSupport as a main dependency (not shale though) which I think is a bit too much, and actually has a performance hit on the methods it provides.

I really think that Ruby community can do better here ?

[1] https://github.com/vasilakisfil/SimpleAMS

[2] https://vasilakisfil.social/blog/2020/01/20/modern-ruby-seri... (scroll towards the end for benchmarks)

Comment · 4 years ago
nice! I use that quite often, so it might come handy. Quick question, how did you build that ? Does Google provide any sort of API or did you build a web scraper for that ?
Comment · 4 years ago
Comment · 4 years ago
Location: Stockholm, Sweden & Athens, Greece

Remote: Yes

Willing to relocate: Maybe

Technologies: Rust, Ruby, Javascript, PostgreSQL, ElasticSearch, Redis, AWS, Networks, APIs, Voip, SIP, SDP, WebRTC

Résumé/CV: https://vasilakisfil.social/public/FilipposVasilakis.pdf

Email: [email protected]

Among others:

* HTTP/REST APIs specialist, pure interest in networked services and optimizations

* Good knowledge of CAS/SAML/OAuth2 and related auth protocols

* Good knowledge of VOIP/SIP/SDP/RTP/WebRTC and related protocols

* Good knowledge of Distributed Systems theory, concepts & principles

Looking for a permanent role, but open to consultancy as well.

Comment · 4 years ago
this is really good idea, how comes not many sites/companies/people use it?
Comment · 4 years ago
This is so depressing, and I am left with just over 60%.I can't imagine how someone would feel with just 10% or even less..
Comment · 4 years ago
for some reason, from the video, screen doesn't feel the same quality as other e-ink readers like kindle.

edit: I mean, kindle videos feel like you are reading a real paper, while here feels like you are in an actual screen.

Comment · 5 years ago
Comment · 5 years ago
In my experience none really cares about your side projects during interviews. I have plenty of side projects, given plenty of talks, I list some of those in my resume along with my github link, yet from 40 interviews I had in the past 5 years I think ~3 mentioned something about my talks and side projects. And definitely didn't give me any advantage over the other interviewers.

But I am fine with that, I do my side projects & talks because I enjoy it and not to increase my chances when applying to a new job. Although there is nothing wrong to do a side project to increase your chances to get a better job.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton