Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
runningmike
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
3 ms
·
1.
▲
by
runningmike
7d ago
100% disagree! Do not mix and cherry pick terms and definitions to make your point. That's not scientific -) Take e.g. a look in https://opensciencemooc.eu/ and check a nice accepted handbook like "The Turing Way
2.
▲
by
runningmike
7d ago
Nice question! Plenty (open) research papers and thesis available the last 40 years -) Some nice papers: https://arxiv.org/pdf/2002.07135 , https://arxiv.org/abs/2411.17343 , https://doi
3.
▲
by
runningmike
8d ago
From a security perspective cc is highly relevant. I use it to get a solid rating of the security aspects of Python code. I use [1] which is solid and proven. [1] https://nocomplexity.com/documents/codeaudit/comple
4.
▲
The PSF Strategic Plan 2026
(pyfound.blogspot.com)
2 points
by
runningmike
9d ago
|
1 comments
5.
▲
by
runningmike
9d ago
"Today we are sharing the outcome: at its July 8 meeting, the PSF Board adopted the PSF Strategic Plan 2026, covering 2026 to 2031." As someone who loves Python, but lives in the EU I see too much emphasis on PyCON_US and US Pytho
6.
▲
by
runningmike
10d ago
The thing is how to deal with principles in practice? Good principles[1] are never trivial. A principle must have implications, some which you can never predict upfront. You will and must have continuous discussing when you use principles t
7.
▲
Soft-Deprecating Re.match()
(hugovk.dev)
2 points
by
runningmike
15d ago
|
0 comments
8.
▲
by
runningmike
15d ago
Read one or more of the absolute best (free) Python books[1] and do some hands-on. If you can not choose, just start with "Python Programming for Data Science". No barrier for starting, its cc-by and requires no account to read. [
9.
▲
by
runningmike
16d ago
Too bad that the focus is open source. This is a common ailment seen in many security research papers! A real concern should be Code-Level Backdoors in COTS software. Backdoors that even many resellers and paying customers are not aware off
10.
▲
by
runningmike
17d ago
Nice deep insight. I love the personal story at the start!
11.
▲
by
runningmike
18d ago
Is this worth watching?
12.
▲
Type Hints in Python Libraries and Frameworks: An Empirical Analysis of Adoption
(arxiv.org)
1 points
by
runningmike
23d ago
|
1 comments
13.
▲
by
runningmike
23d ago
Full title: "Type Hints in Python Libraries and Frameworks: An Empirical Analysis of Adoption and Maintenance" Conclusion: Type hints in Python libraries and frameworks primarily serve as API contracts rather than comprehensive d
14.
▲
A Comprehensive Study of Native Code Bugs in Python Applications
(arxiv.org)
1 points
by
runningmike
25d ago
|
1 comments
15.
▲
by
runningmike
25d ago
" In this paper, we set out to fill this critical gap, focusing on real-world native code bugs in native Python applications (i.e., software written in Python and C as primary languages, a.k.a Python-C software). We start by collecting
16.
▲
by
runningmike
25d ago
Nice improvement! Good reliable statistics for Python package use is a real challenge! So best is to use multiple indicators to get a rough indication! "This change removes one source of potential confusion and misinterpretation, but d
17.
▲
by
runningmike
26d ago
Some context and nuance: https://support.mozilla.org/en-US/kb/use-primary-password-pr...
18.
▲
by
runningmike
29d ago
Nice insight in cost involved with a huge free to use systems, Drupal! I think it is always better to make a clear distinguish between FOSS and OSS. Just to avoid these kind of issues in discussions again and again!
19.
▲
Open Source is a cost-allocation system
(dri.es)
1 points
by
runningmike
29d ago
|
1 comments
20.
▲
by
runningmike
1mo ago
Great to see this! Nice work.
21.
▲
The Python documentation is now available in Russian
(blog.python.org)
2 points
by
runningmike
1mo ago
|
1 comments
22.
▲
by
runningmike
1mo ago
I'll still see many languages still not supported. Translating the Python Docs in another language and maintaining it , is a hell of a job. Nice too see this!
23.
▲
by
runningmike
1mo ago
Nice to see this! Personally, I prefer CC BY-SA to CC BY-NC-ND, but it is certainly much better than 100% protected. Over the years, I've built and maintain a list[1] of CC BY-SA Python books that have no access barriers, such as manda
24.
▲
The global race to make a practical quantum computer took a big leap forward
(theconversation.com)
3 points
by
runningmike
1mo ago
|
0 comments
25.
▲
Ironic-Python-Agent: Container HardwareManager Security Model Misimplemented
(seclists.org)
2 points
by
runningmike
1mo ago
|
0 comments
26.
▲
Beyond Source: An Empirical Study of Python Bytecode Security Risks
(arxiv.org)
2 points
by
runningmike
1mo ago
|
0 comments
27.
▲
an ambiguity in C89 which will never be fixed
(sebsite.pw)
72 points
by
runningmike
2mo ago
|
46 comments
28.
▲
by
runningmike
2mo ago
“ the agent ran Tailscale with --no-logs-no-support, which suppresses reporting from that client. That's an option designed for users who are concerned about sending telemetry metadata to Tailscale.” And imho a serious security archite
29.
▲
by
runningmike
2mo ago
"Our anomaly-detection pipeline uses LLM-based triage over security telemetry to separate real signals from the daily noise, and it was the correlation of those signals that flagged the compromise." After reading https:/
30.
▲
by
runningmike
2mo ago
Looks nice and interesting. Do you have a repository to the code?
More ›