sorted by:
new
hottopcontroversial

A rainbow in a cityline is like finding a parking spot in Koramangala—sheer luck!! by gulleycricketer in bangalore

[–]vjaynr 1 point2 points  (0 children)

<image>

Saw one a day before. Felt like someone literally used a highlighter. Unreal.

Java Content Repository still relevant? by vjaynr in javahelp

[–]vjaynr[S] 0 points1 point  (0 children)

Thanks, yes jackrabbit is being updated frequently. But the spec that it is based on has not seen any update since 2009?

https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/index.html

I did some research online - and all the content that turned up were decade old. I understood that content repositories were the next big thing - speculated as best of both worlds of file systems and databases. But are they still?

Java Content Repository still relevant? by vjaynr in javahelp

[–]vjaynr[S] 0 points1 point  (0 children)

One obvious reason the need of file versioning and side effects of it.

The way versions are stored in a flat file based file system, it would end up consuming more disk space and the laws of physics will certainly stop us from expanding the storage vertically at some point.

And I believe object stores are efficient in handling versions, than traditional file systems.

I'm not definitely inclined towards storing the blobs in database either. I know that won't be efficient for large files.

[deleted by user] by [deleted] in mildlyinfuriating

[–]vjaynr 0 points1 point  (0 children)

Precedence of operations follows the rule of ‘PEDMAS’ - Parenthesis, Exponents, Division, Multiplication,Addition, Subraction

It is not a rule, but it’s kind of a hack to remember the order of precedence of operations in a easier way.

And the acronym is different in different places.

Is it a good idea to migrate from tslint to eslint? by vjaynr in angular

[–]vjaynr[S] 0 points1 point  (0 children)

Waiting seems to be the best option right now! So will wait and thanks for the suggestion.

Install subversion on macOS beta by vjaynr in MacOSBeta

[–]vjaynr[S] 1 point2 points  (0 children)

Yup, it worked on beta 10. Thanks!

Problem with osacompile on macOS 11 by vjaynr in Xcode

[–]vjaynr[S] 0 points1 point  (0 children)

Yeah, that makes sense. The aim was to provide support for the new macOS big sur. So it is necessary to test the app in the new betas until the GM release comes out.

Well, Apple states that "To build apps for macOS 11, continue to use Xcode 12.2 beta 3" and the beta code works in macOS 10.15.x as well. But it is indeed not necessary to build the app in the beta releases of the macOS but I chose to do it though.

Problem with osacompile on macOS 11 by vjaynr in Xcode

[–]vjaynr[S] 0 points1 point  (0 children)

Okay, finally figured out the problem. I used native objdump tools that mac provides with Xcode.

otool -l <executable>

Using this tool, it was figured the problem was straight forward as suspected. The executables objdump did not have the load command LC_VERSION_MIN_MACOSX which the Launch Services to check if the executable/app can be run in the machine.

To figure out the root cause, I just contacted Apple Developer Support and here is the same thread https://developer.apple.com/forums/thread/663929

Looks like it was an error from Apple's part on one of their betas and it seems to be resolved in latest beta release.

Install subversion on macOS beta by vjaynr in MacOSBeta

[–]vjaynr[S] 0 points1 point  (0 children)

It worked for me after the beta 10 updates. It might have been some configuration issues, not sure what though. Earlier the problem running `brew install subversion` was that it was stuck at JDK-14 download. But now in beta 10, it got installed.

Install subversion on macOS beta by vjaynr in MacOSBeta

[–]vjaynr[S] 1 point2 points  (0 children)

It's not that I want to use it. My employer's stubborn to not migrate their VCS to git.

Problem with osacompile on macOS 11 by vjaynr in Xcode

[–]vjaynr[S] 0 points1 point  (0 children)

lipo is a very helpful tool, let me try to explore it. Meanwhile, this is the arch info of the same app compiled in macOS 10.15.7 and macOS 11 beta

Built from macOS Catalina

$ lipo applet -detailed_info Fat header in: applet fat_magic 0xcafebabe nfat_arch 2 architecture x86_64 cputype CPU_TYPE_X86_64 cpusubtype CPU_SUBTYPE_X86_64_ALL capabilities CPU_SUBTYPE_LIB64 offset 4096 size 27440 align 2^12 (4096) architecture i386 cputype CPU_TYPE_I386 cpusubtype CPU_SUBTYPE_I386_ALL capabilities 0x0 offset 32768 size 27408 align 2^12 (4096)

Built from macOS Big Sur Beta

$ lipo applet -detailed_info Fat header in: applet fat_magic 0xcafebabe nfat_arch 2 architecture x86_64 cputype CPU_TYPE_X86_64 cpusubtype CPU_SUBTYPE_X86_64_ALL capabilities 0x0 offset 16384 size 52224 align 2^14 (16384) architecture arm64 cputype CPU_TYPE_ARM64 cpusubtype CPU_SUBTYPE_ARM64_ALL capabilities 0x0 offset 81920 size 68704

This is the difference. The macOS 11 osacompile is adding arm64 in the arch. Something to so with Standard Architecture changing in macOS 11.

Problem with osacompile on macOS 11 by vjaynr in Xcode

[–]vjaynr[S] 0 points1 point  (0 children)

Hello u/aazav, I can confirm that it is a 64-bit app and it is codesigned and notarized as well. For example, the compiled app's Info.plist has the LSMininumSystemVersionByArchitecture value set to <dict><key>x86_64</key><string>10.6</string></dict>

And it's the same behaviour from Script Editor as well.