Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vasilakisfil
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
91.
▲
An unorthodox approach to Ruby performance profiling when everything else fails
(blog.kollegorna.se)
1 points
by
vasilakisfil
9y ago
|
0 comments
92.
▲
by
vasilakisfil
9y ago
We have been using kemal in small projects and we are super happy with it. In my company that I am working for we are evaluating crystal and elixir as the next language to start investing/developing (we are on Ruby/Rails now). 2 t
93.
▲
3+ years of Ember, 6 months of React
(blog.kollegorna.se)
5 points
by
vasilakisfil
9y ago
|
0 comments
94.
▲
by
vasilakisfil
9y ago
From my personal experience Spotify has really bad recommendations, even YouTube has better ones.
95.
▲
by
vasilakisfil
9y ago
Ember is much easier to pickup than React + Redux + React-Router for a SPA. You just create a couple of routes and add some HTML and you are done. 5 minutes later you can deploy. In React you would need at least an hour (if not a day) in we
96.
▲
Dropbox please add a goddamn delete button
(blog.fil.vasilak.is)
2 points
by
vasilakisfil
9y ago
|
0 comments
97.
▲
by
vasilakisfil
9y ago
You can use Introspected REST ( https://introspected.rest ) that allows you to fine-tune and balance between REST and GraphQL. No available libraries at the moment that can help you though so this could be a problem for your use c
98.
▲
by
vasilakisfil
9y ago
The same could have been said 30 years ago for an open source OS.
99.
▲
by
vasilakisfil
9y ago
Facebook is just dying and they know that from their internal metrics long time now so these features have been developed to save the engagement because otherwise facebook's stock value will plange.
100.
▲
by
vasilakisfil
9y ago
REST allows you to change the structure of the data as well, for instance using linked-data specs, like schema.org. However, in practice it's very difficult and also REST makes it very difficult to evolve different parts of the API, as
101.
▲
by
vasilakisfil
9y ago
RPC is not evolvable neither self descriptive so it's very difficult to introduce changes on API used by remote clients, without human interaction.
102.
▲
Introspected REST: An Alternative to REST and GraphQL
(introspected.rest)
1 points
by
vasilakisfil
9y ago
|
4 comments
103.
▲
by
vasilakisfil
9y ago
Hi, author here. Introspected REST is a new model for evolvable networked services. It's an alternative to Roy's REST (and GraphQL). In youtube there is a related talk I had given about a year ago called "Sliding away from Ro
104.
▲
Introspected REST: An alternative to REST and GraphQL
(github.com)
1 points
by
vasilakisfil
9y ago
|
1 comments
105.
▲
by
vasilakisfil
9y ago
Just curious: if they solve it in Python, would it be possible to solve it in Ruby too ?
106.
▲
by
vasilakisfil
9y ago
ok depends on the size of a feature I guess but usually I sit in a branch for 2-3 days before I finish the feature. Also what's the point of preserving the history of a branch that is used for the development of a requested feature ? F
107.
▲
by
vasilakisfil
9y ago
I have been using that in every branch: I commit regularly and end up with 10+ commits. Then I rebase + squash them and at the same time write a summary commit. Eventually I merge. This has multiple good effects. First, you get a clean, fe
108.
▲
REST is all about evolvability
(blog.fil.vasilak.is)
2 points
by
vasilakisfil
9y ago
|
1 comments
109.
▲
We need better compartmentalization
(blog.fil.vasilak.is)
1 points
by
vasilakisfil
9y ago
|
0 comments
110.
▲
by
vasilakisfil
9y ago
Yes Ember-Data was great thing to have in Ember, something I miss from React ecosystem. In the early days was a bit unstable but now it's super stable and flexible (serializers/adapters customization etc). I think there should be
111.
▲
by
vasilakisfil
10y ago
I would love the same app for tennis partners :)
112.
▲
Rack-reqorder: Metrics, exceptions and request/response monitoring for rack
(labs.kollegorna.se)
1 points
by
vasilakisfil
10y ago
|
0 comments
113.
▲
What travelling have taught me so far…
(vassilakisv.wordpress.com)
2 points
by
vasilakisfil
10y ago
|
0 comments
114.
▲
Build an API in your Rails app now (Rails 5 version)
(github.com)
1 points
by
vasilakisfil
10y ago
|
0 comments
115.
▲
by
vasilakisfil
10y ago
The site does not use HTTPS (TLS) so that public key is completely useless.
116.
▲
by
vasilakisfil
10y ago
SIP is open, but none uses it :/ That's why I feel pushing for open standards is the key: it will allow you to install any voip app as long as it is compatible (follows the open standards).
117.
▲
by
vasilakisfil
10y ago
It's unbelievable that we are moving to 100% Internet area, regular phones are deprecated, yet we are full of Silos. Skype user can't call Google hangouts user, Facebook user can't talk to Twitter user. Imagine what would hap
118.
▲
by
vasilakisfil
10y ago
A global VOIP service that is based on open standards. Or an open social network, also based on open standards. Both should be extensible.
119.
▲
Rendering Ember components from Rails
(labs.kollegorna.se)
2 points
by
vasilakisfil
10y ago
|
0 comments
120.
▲
by
vasilakisfil
10y ago
emberjs, it has strong convention over configuration and you can speed up easily.
More ›