bvrmn

40 ms·

601.
by bvrmn 7y ago
May be I was unclear. If we introduce record abstraction for file ops then OS low-level implementation have to decide which way to store structured data. meta + payload or meta separated from payload. In latter case there is no way to provi
602.
by bvrmn 7y ago
What to do with clients who want a stream of records? Separated meta + payload allows fast byte streams. Combined meta + payload allows fast record streams. Structured implementation can't provide performance for both cases. But byte-o
603.
by bvrmn 7y ago
> Implementing streaming files over record-based files is easier What a performance-wise nightmare. Goodbye page cache and other zero copy optimizations.
604.
by bvrmn 7y ago
It's more convenient to call and export needed function directly via C API than force everybody to make and use another "universal" layer.
605.
by bvrmn 7y ago
No, by default library allow "none" alg. And there is no mandatory option to limit algs. Your foot is no more. var DEFAULT_OPTIONS = { algorithms: "*", allowEmbeddedKey: false };
606.
by bvrmn 7y ago
There is a very entertaining discussion about fs-as-db-and-more from core linux devs: https://yarchive.net/comp/linux/reiser4.html .
607.
by bvrmn 7y ago
Article resume: biggest cs problem now is a diversity of serialization formats, because most of current code consist of parsing various formats, so OS must to do something about it. No, it is not a so big problem. And no it will not do our
608.
by bvrmn 7y ago
Symmetric signatures completely kill ability to verify token without secret. For python I had to glue and stick python_jwt with cryptography primitives to do ed25519. And the most funny thing: very few clients will understand these "st
609.
by bvrmn 7y ago
> JWS/JWT supports Support for ed25519 signature in current implementations is pretty poor.
610.
by bvrmn 7y ago
Yes, we have fast CPUs now, lets burn these idle cycles for distracting icon animations! (OP article page fully loads 1 cpu core).
611.
by bvrmn 7y ago
Zig has a very small "core" idea. Explicit allocator, basic C semantics, clear UB, errors and comptime. All other features implemented in stdlib in zig itself. Odin fills like go with "special" runtime. For example dynam
612.
by bvrmn 7y ago
> What when allocation fails or disk full etc? It is a common misconception that such errors can be easily handled. Most of software is too complex to be able to do something reliable with hard OS issues. Stack unwiding with exceptions i
613.
by bvrmn 7y ago
No, article corresponds to unicorn-rainbow-coin-rebel style of most hackernoon content very well.
614.
by bvrmn 7y ago
Error propagation is must have for any project. You always need to handle some errors in parent context because local knowledge can be not enough. And you can choose between manual passing of error codes (c, go, mundane and boiler-platy), a
615.
by bvrmn 7y ago
These are made up rules in your head. If you can deal with OS global state, you can deal with any global state and keep clean BL.
616.
by bvrmn 7y ago
> but suffers from its design around global state - which is something I spend most of the semester railing against. You can introduce subject as another execution environment like OS and keep globals-free "clean" code. Actuall
617.
by bvrmn 7y ago
There is no difference between OS level global state and framework level global state. Students and teacher are free to create clean abstractions on top of any global state. Why are we tolerable to OS boundary and not tolerable to in-proces
618.
by bvrmn 7y ago
To give the individual tests import context, create a tests/context.py file: import os import sys sys.path.insert(0, os.path.abspath(os.path.join(os.path.dirname(__file__), '..'))) Or you can convert your tests
619.
by bvrmn 7y ago
Also this comes to mind. Most of successful IT companies do not use external services for core components and prefer inhouse solutions.
620.
by bvrmn 7y ago
> Interfaces between teams updated with every application change. Dev products do not solve issues of bad architecture. It will be same struggle but in more strong form.
621.
by bvrmn 7y ago
Most real data is too big to fetch in one piece by a client. Internal admin interfaces come to mind. On each job every time support people ask to include monstrous sorting behavior over multiple columns to be able to find group in question.
622.
by bvrmn 7y ago
Good searching and filtering should be on the first place. May be you don't need long tabular presentation at all because of this.
623.
by bvrmn 7y ago
Python has built-in facilities for that, there is no need to write wrapper by yourself. from functools import partial with open('mydata.db', 'rb') as f: for block in iter(partial(f.read, 64), b''
624.
by bvrmn 7y ago
You chose a very bad example for "imperative code". It seems artificially complicated. def fib(n: int) -> int: prev, cur = 0, 1 for _ in range(n-1): prev, cur = cur, prev + cur return c
625.
by bvrmn 7y ago
All "cleverness" usually comes from struggle with parser generator. It's too many languages in the wild with weird syntax due to lack of interest/skills in proper parser.
626.
by bvrmn 7y ago
Format string is very inconvenient approach because you need to duplicate type information. >>> '%i' % 's' Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError
627.
by bvrmn 7y ago
Article on bloomberg wants to make something public and wants money from me simultaneously.
628.
by bvrmn 7y ago
I see. My original comment was not clear. I also use queues a lot in my systems. But only as implementation detail and it helps to solve scalability and persistence problems. Message bus proponents like to place common bus as central medium
629.
by bvrmn 7y ago
Message bus proponents never build large systems. The only sane way is to be pretty specific about data flow with clear mental model shared between developers and ops. Message bus hides producer-consumer relations and with multiple endpoint
630.
by bvrmn 8y ago
There is a 7th main factor. You should have multiple teams. It's sad how most of pro-microservice articles forget to mention this point explicitly. For most IT companies microservices don't make sense at all.

More ›